Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-48717 – OAuth PKCE Authorization Bypass – OpenAM before 16.1.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-48717 is an improper authorization vulnerability (CWE-285) in OpenAM’s OAuth2 authorization-code grant handling that allows a PKCE-protected authorization code to be redeemed without supplying the required code_verifier. It affects OpenAM Community Edition versions through 16.0.6 and carries a CVSS v4.0 base score of 9.1 (Critical).

Technical details

  • OpenAM’s authorize endpoint stores a code_challenge on the issued authorization code when a client initiates a PKCE (Proof Key for Code Exchange) flow.
  • The token endpoint only enforces validation of the corresponding code_verifier when a realm-wide setting, codeVerifierEnforced, is explicitly turned on — and this setting ships disabled by default.
  • With enforcement off, the stored code_challenge is checked only if the client actually supplies a code_verifier; an attacker who omits the parameter entirely bypasses PKCE verification.
  • Attack vector is network-based and requires no user interaction beyond intercepting or otherwise obtaining a valid authorization code (e.g., via an OAuth redirect leak). Public clients relying solely on PKCE for protection are most exposed, since an intercepted code can be exchanged directly for tokens without any additional secret.
  • Successful exploitation results in unauthorized redemption of authorization codes for access/ID tokens, impacting confidentiality and integrity of the OAuth2 flow.

Affected software

  • OpenIdentityPlatform OpenAM, all versions up to and including 16.0.6

Severity

  • CVSS v4.0 Base Score: 9.1 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade OpenAM to version 16.1.1 or later, which enforces PKCE code_verifier validation correctly.
  • If patching is not immediately possible: Explicitly enable the realm-wide codeVerifierEnforced setting for all realms using PKCE-based OAuth2 clients so that authorization codes with a stored code_challenge cannot be redeemed without a matching code_verifier. Review OAuth2 client configurations to ensure public clients are not relying solely on default settings for PKCE protection.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge