OpenAM before 16.1.3 applies its OAuth2 Provider PKCE enforcement only to authorization requests whose response_type is exactly code, so codes issued through OpenID Connect hybrid flows (code token, code id_token, code token id_token) carry no bound challenge. An attacker who intercepts such a code can redeem it for a public client's tokens with any non-empty code_verifier.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Sat, 03 Oct 2026 14:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | OpenAM before 16.1.3 applies its OAuth2 Provider PKCE enforcement only to authorization requests whose response_type is exactly code, so codes issued through OpenID Connect hybrid flows (code token, code id_token, code token id_token) carry no bound challenge. An attacker who intercepts such a code can redeem it for a public client's tokens with any non-empty code_verifier. | |
| Title | OpenAM before 16.1.3 PKCE Enforcement Bypass via OAuth 2.0 Hybrid Flows | |
| First Time appeared |
Openidentityplatform
Openidentityplatform openam |
|
| Weaknesses | CWE-285 | |
| CPEs | cpe:2.3:a:openidentityplatform:openam:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Openidentityplatform
Openidentityplatform openam |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: VulnCheck
Published:
Updated: 2026-10-03T12:14:43.643Z
Reserved: 2026-10-03T12:04:36.964Z
Link: CVE-2026-105119
No data.
Status : Received
Published: 2026-10-03T14:16:38.710
Modified: 2026-10-03T14:16:38.710
Link: CVE-2026-105119
No data.
OpenCVE Enrichment
Updated: 2026-10-03T15:30:19Z
Weaknesses