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
Trending — 3 sources updated this week
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%CVSS: 9.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.1(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

June 29, 2026

Last Modified

September 15, 2026

Advisory Details (3)

Auto-updated Sep 15, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

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 rangeFixed inDependents
org.openidentityplatform.openam:openam-oauth214.5.2 ... 16.1.0 (40 versions)16.1.1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 06:57 UTCEG score recompute
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-15 14:37 UTCEG score recompute
  6. 2026-09-15 13:58 UTCEG score recompute
  7. 2026-09-15 10:28 UTCEG score recompute
  8. 2026-09-15 10:03 UTCEG score recompute 9.10
  9. 2026-09-15 10:02 UTCMITRE cvelistV5CVSS v3 → 9.1 · CVSS v4 → 9.1 · severity → CRITICAL
  10. 2026-08-01 13:36 UTCEG score recompute
  11. 2026-07-26 14:02 UTCEG score recompute
  12. 2026-07-23 03:18 UTCEG score recompute
  13. 2026-06-29 18:05 UTCEG score recompute

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 in the National Vulnerability Database on June 29, 2026, with the most recent update on September 15, 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% probability of exploitation in the next 30 days, which ranks it in the top 74.0% of all scored CVEs.
What is the CVSS score of CVE-2026-48717?
CVE-2026-48717 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-48717?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48717, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.