OpenAM OAuth Client Impersonation via JWKS Resolver Cache (CVE-2026-47426) | HOL Guard CVE

High severityCVE-2026-47426GHSA-F2CX-463Q-7M2C

OpenAM OAuth Client Impersonation via JWKS Resolver Cache

Answer in brief

CVE-2026-47426 records a High severity vulnerability in OpenAM OAuth Client Impersonation via JWKS Resolver Cache. The current sources do not mark it as known exploited. The current feed maps OpenIdentityPlatform/OpenAM (generic), org.openidentityplatform.openam:openam-oauth2 (maven), org.openidentityplatform.openam:openam-oauth2 (maven). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 15, 2026Updated Sep 15, 2026Source checked Sep 17, 2026First seen by HOL Jun 29, 2026Material review Sep 15, 2026

Upstream Advisory

Key facts

Risk: High
Exploitation: Not marked as known exploited
Affected software: 3 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps OpenIdentityPlatform/OpenAM (generic), org.openidentityplatform.openam:openam-oauth2 (maven), org.openidentityplatform.openam:openam-oauth2 (maven). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
OpenIdentityPlatform/OpenAMgeneric	< 16.1.1	Not reported
org.openidentityplatform.openam:openam-oauth2maven	<=16.0.6	16.1.1
org.openidentityplatform.openam:openam-oauth2maven	>=0 <16.1.1	16.1.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for OpenIdentityPlatform/OpenAM, org.openidentityplatform.openam:openam-oauth2, org.openidentityplatform.openam:openam-oauth2.
Review the reported fix. Update org.openidentityplatform.openam:openam-oauth2 to 16.1.1; org.openidentityplatform.openam:openam-oauth2 to 16.1.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 15, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jun 29, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.