CVE-2026-105119: OpenIdentityPlatform OpenAM · Improper Authorization
Affects OpenIdentityPlatform OpenAMSource CVE Database V5
Not known to be exploited · CVSS 7.6 High : upgrade to 16.1.3 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 16.1.3
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade OpenAM and openidentityplatform/OpenAM to 16.1.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| OpenIdentityPlatformOpenAM | Affected
| Fixed in
|
GitHubopenidentityplatform/OpenAMpkg:github/openidentityplatform/OpenAMOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in OpenAM version 16.1.3 that properly enforces PKCE on all OAuth2 authorization requests, including hybrid OpenID Connect flows. Users should upgrade to version 16.1.3 or later to remediate this issue.
Description
OpenAM versions before 16.1.3 have an improper authorization vulnerability in their OAuth2 Provider implementation. Specifically, PKCE enforcement is only applied to authorization requests with response_type exactly equal to 'code'. Hybrid OpenID Connect flows that include 'code token', 'code id_token', or 'code token id_token' do not have this enforcement, allowing intercepted authorization codes to be redeemed by attackers with any non-empty code_verifier.