OpenAM OAuth Client Impersonation via JWKS Resolver Cache

高危 7.6CVE-2026-47426 · GHSA-f2cx-463q-7m2c · Published 15/09/2026 · updated 23/09/2026

要点

CVE-2026-47426 是影响 org.openidentityplatform.openam:openam-oauth2 的高危 (CVSS 7.6)漏洞。
未来 30 天内被利用的概率（EPSS）：0.55%，高于 46.3% 的漏洞。
修复：升级到 16.1.1 或更高版本。

Package	Affected versions	Patched versions
org.openidentityplatform.openam:openam-oauth2 Maven	`< 16.1.1`	`16.1.1`

Description

Summary

Description

An Improper Authentication (CWE-287) issue in OpenAM's OAuth2 private_key_jwt client authentication path allows any registered OAuth2 client to mint tokens in the name of any other client whose key is published via a jwks_uri, without knowing the victim's signing key. This affects OpenAM Community Edition through version 16.0.6 and was patched in version 16.1.1.

Impact

OpenAM Community Edition deployments through version 16.0.6 that have OAuth2 clients configured for private_key_jwt authentication with keys published via jwks_uri are potentially affected. An attacker holding any such client registration, their own, or one obtained through open dynamic client registration where enabled, can mint access tokens in any other such client's name, in any realm hosted by the OpenAM process.

Patch

This has been patched in OpenAM Community Edition version 16.1.1. Users are encouraged to update to the latest release.

NVD 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.