OpenAM OAuth Authorization Bypass via PKCE Challenge (CVE-2026-48717) | HOL Guard CVE

Medium severityCVE-2026-48717GHSA-4V2W-2WQP-MC85

OpenAM OAuth Authorization Bypass via PKCE Challenge

Answer in brief

CVE-2026-48717 records a Medium severity vulnerability in OpenAM OAuth Authorization Bypass via PKCE Challenge. The current sources do not mark it as known exploited. The current feed maps OpenIdentityPlatform/OpenAM (generic), org.openidentityplatform.openam:openam-oauth2 (maven), org.openidentityplatform.openam:openam-oauth2 (maven). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 15, 2026Updated Sep 15, 2026Source checked Sep 17, 2026First seen by HOL Jun 29, 2026Material review Sep 15, 2026

Upstream Advisory

Key facts

Risk: Medium
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps OpenIdentityPlatform/OpenAM (generic), org.openidentityplatform.openam:openam-oauth2 (maven), org.openidentityplatform.openam:openam-oauth2 (maven). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
OpenIdentityPlatform/OpenAMgeneric	< 16.1.1	Not reported
org.openidentityplatform.openam:openam-oauth2maven	<=16.0.6	16.1.1
org.openidentityplatform.openam:openam-oauth2maven	>=0 <16.1.1	16.1.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for OpenIdentityPlatform/OpenAM, org.openidentityplatform.openam:openam-oauth2, org.openidentityplatform.openam:openam-oauth2.
Review the reported fix. Update org.openidentityplatform.openam:openam-oauth2 to 16.1.1; org.openidentityplatform.openam:openam-oauth2 to 16.1.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jun 29, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.