CVE-2026-48717

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 74% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • 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 intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

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.
githubMentions 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.

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 7× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:18 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-01 19:50 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-27 13:48 UTCEPSS rescore
  13. 2026-09-26 15:59 UTCEPSS rescore
  14. 2026-09-26 00:27 UTCEPSS rescore
  15. 2026-09-23 19:06 UTCEG score recompute
  16. 2026-09-23 17:53 UTCEPSS rescore
  17. 2026-09-23 07:29 UTCEG score recompute
  18. 2026-09-20 20:16 UTCEPSS rescore
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-18 06:57 UTCEG score recompute
  21. 2026-09-16 14:08 UTCEPSS rescore
  22. 2026-09-16 05:15 UTCEPSS rescore
  23. 2026-09-15 14:37 UTCEG score recompute
  24. 2026-09-15 13:58 UTCEG score recompute
  25. 2026-09-15 10:28 UTCEG score recompute
Show 6 more
  1. 2026-09-15 10:03 UTCEG score recompute▲ 9.10
  2. 2026-09-15 10:02 UTCMITRE cvelistV5CVSS v3 → 9.1 · CVSS v4 → 9.1 · severity → CRITICAL
  3. 2026-08-01 13:36 UTCEG score recompute
  4. 2026-07-26 14:02 UTCEG score recompute
  5. 2026-07-23 03:18 UTCEG score recompute
  6. 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 vulnerability published on June 29, 2026. Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, AuthorizationCodeGrantTypeHandler requires a codeverifier only when the realm-wide codeVerifierEnforced setting is enabled, even when an authorization code stores a codechallenge. Because that setting is disabled by…
When was CVE-2026-48717 disclosed?
CVE-2026-48717 was first published on June 29, 2026, with the most recent update on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 (43rd 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