CVE-2026-48717

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-78369 (ENISA EUVD) · GHSA-4v2w-2wqp-mc85 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, AuthorizationCodeGrantTypeHandler requires a code_verifier only when the realm-wide codeVerifierEnforced setting is enabled, even when an authorization code stores a code_challenge. Because that setting is disabled by default, an attacker who intercepts a PKCE-protected authorization code can omit code_verifier and redeem the code, while an explicitly incorrect verifier is rejected. Public clients are directly affected, and confidential-client exploitation additionally requires client authentication material or another redemption context. This issue is fixed in version 16.1.1.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 29, 2026

Last Modified

September 23, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

OpenAM OAuth Authorization Bypass via PKCE Challenge · Advisory · OpenIdentityPlatform/OpenAM · GitHub

Affected: version 16.1.1.

https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-4v2w-2wqp-mc85
GitHub release Patch Available

16.1.1

Patch available: OpenIdentityPlatform/OpenAM 16.1.1

https://github.com/OpenIdentityPlatform/OpenAM/releases/tag/16.1.1
GitHub commit

commit 97a34d9fee17 (OpenIdentityPlatform/OpenAM)

Fix landed in OpenIdentityPlatform/OpenAM commit 97a34d9fee17 — awaiting tagged release

https://github.com/OpenIdentityPlatform/OpenAM/commit/97a34d9fee17395e8e052bfc45eb5855f436153e

Vendor Advisories for CVE-2026-48717(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.openidentityplatform.openam:openam-oauth2 @ 16.1.1 (fixes <= 16.0.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.openidentityplatform.openam:openam-oauth214.5.2 ... 16.1.0 (40 versions)
  • every version up to 16.1.1: fixed in 16.1.1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 55× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 18:10 UTCEG score recompute
  2. 2026-11-01 18:10 UTCGHSA enrichmentGHSA-4v2w-2wqp-mc85 · GitHub severity MODERATE
  3. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-11-01 07:47 UTCGHSA enrichmentGHSA-4v2w-2wqp-mc85 · GitHub severity MODERATE
  5. 2026-10-31 17:43 UTCEG score recompute
  6. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-10-30 17:16 UTCEG score recompute
  8. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  9. 2026-10-29 16:49 UTCEG score recompute
  10. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-10-28 16:20 UTCEG score recompute
  13. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-10-27 15:53 UTCEG score recompute
  15. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-10-26 15:23 UTCEG score recompute
  17. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-25 14:10 UTCEG score recompute
  19. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-24 13:43 UTCEG score recompute
  21. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-23 13:17 UTCEG score recompute
  23. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-22 12:51 UTCEG score recompute
  25. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 54 more
  1. 2026-10-21 12:23 UTCEG score recompute
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-10-20 11:57 UTCEG score recompute
  4. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-19 11:29 UTCEG score recompute
  6. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  7. 2026-10-18 03:34 UTCEG score recompute
  8. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-17 07:56 UTCEG score recompute
  10. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-16 07:28 UTCEG score recompute
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-15 06:22 UTCEG score recompute
  14. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-14 02:03 UTCEG score recompute
  16. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-12 22:22 UTCEG score recompute
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-10-12 16:00 UTCEG score recompute
  20. 2026-10-11 19:43 UTCEG score recompute
  21. 2026-10-11 16:58 UTCEG score recompute
  22. 2026-10-11 14:22 UTCEG score recompute
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  26. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  27. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  28. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  29. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  30. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  31. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  32. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  33. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  34. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  35. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  37. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  38. 2026-09-23 19:06 UTCEG score recompute
  39. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  40. 2026-09-23 07:29 UTCEG score recompute
  41. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  42. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  43. 2026-09-18 06:57 UTCEG score recompute
  44. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  45. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  46. 2026-09-15 14:37 UTCEG score recompute
  47. 2026-09-15 13:58 UTCEG score recompute
  48. 2026-09-15 10:28 UTCEG score recompute
  49. 2026-09-15 10:03 UTCEG score recomputeFirst assessed: 9.1 CRITICAL
  50. 2026-09-15 10:02 UTCMITRE cvelistV5CVSS v3 → 9.1 · CVSS v4 → 9.1 · severity → CRITICAL
  51. 2026-08-01 13:36 UTCEG score recompute
  52. 2026-07-26 14:02 UTCEG score recompute
  53. 2026-07-23 03:18 UTCEG score recompute
  54. 2026-06-29 18:05 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-48717?
CVE-2026-48717 is a critical-severity vulnerability; its CVE record was published on June 29, 2026. Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, AuthorizationCodeGrantTypeHandler requires a code_verifier only when the realm-wide codeVerifierEnforced setting is enabled, even when an authorization code stores a code_challenge. Because that setting is disabled…
When was the CVE record for CVE-2026-48717 published?
The CVE record for CVE-2026-48717 was published on June 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 23, 2026; the record at its source may have been updated since.
Is CVE-2026-48717 actively exploited?
CVE-2026-48717 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48717?
CVE-2026-48717 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48717?
A fix for CVE-2026-48717 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48717 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48717

Explore →

Is Your Infrastructure Affected by CVE-2026-48717?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs