Summary
OpenAM OAuth Client Impersonation via JWKS Resolver Cache
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.
The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This has been patched in OpenAM Community Edition version 16.1.1. Users are encouraged to update to the latest release.
Frequently Asked Questions
- What is CVE-2026-47426? CVE-2026-47426 is a high-severity improper authentication vulnerability in org.openidentityplatform.openam:openam-oauth2 (maven), affecting versions <= 16.0.6. It is fixed in 16.1.1. The application does not adequately verify the identity of a user, device, or process before granting access.
- Which versions of org.openidentityplatform.openam:openam-oauth2 are affected by CVE-2026-47426? org.openidentityplatform.openam:openam-oauth2 (maven) versions <= 16.0.6 is affected.
- Is there a fix for CVE-2026-47426? Yes. CVE-2026-47426 is fixed in 16.1.1. Upgrade to this version or later.
- Is CVE-2026-47426 exploitable, and should I be worried? Whether CVE-2026-47426 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-47426 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-47426? Upgrade
org.openidentityplatform.openam:openam-oauth2to 16.1.1 or later.