CVE-2026-47426

published 15 Sep 2026 · updated 18 Nov 2026

OpenAM OAuth Client Impersonation via JWKS Resolver Cache

7.6HighCVSS 7.6EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 16.1.1.

Open Access Management (OpenAM) is an access management solution. Prior to 16.1.1, the private_key_jwt client authentication path uses ClientJwksResolverCache without reliably binding a cached jwks_uri resolver and verified assertion to the expected clientID in ClientCredentialsReader. An attacker controlling any registered client with published keys, including one obtained through open dynamic registration when enabled, can authenticate as another client whose keys are exposed through jwks_uri and mint tokens in that client's name across realms in the same OpenAM process. This issue is fixed in version 16.1.1.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
OpenIdentityPlatformopenam<16.1.116.1.1
OpenIdentityPlatform<16.1.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-47426 severity on Zeptric[![CVE-2026-47426](https://zeptric.io/badge/cve/CVE-2026-47426.svg)](https://zeptric.io/cve/CVE-2026-47426)