CVE-2026-47426

High

Description

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.

SeverityHigh
CVSS7.6
Exploit probability—
ProductOrg.openidentityplatform.openam:openam-oauth2
PublishedSep 15, 2026
First seenSep 15, 2026

How to fix

Update
  • org.openidentityplatform.openam:openam-oauth216.1.1 or later

Affected products

ProductAffected versionsFixed in
org.openidentityplatform.openam:openam-oauth2Mavenv < 16.1.116.1.1

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.