CVE-2026-47426

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering.

Exploit odds

0.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-15 10:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-23 18:19 UTC Last updatedMost recent change to the record

Details

Published

2026-09-15 10:17 UTC

Last modified

2026-09-23 18:19 UTC

Exploit probability

0.6% · EPSS, next 30 days

Weakness

CWE-287 · Improper authentication

Record status

Awaiting Analysis

Attack profile CVSS 4.0 · 7.6

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

Low

User interaction

None

Confidentiality

High

Integrity

High

Availability

None