OAuth client impersonation via unbound JWKS cache
Published Sep 15, 2026 · Updated Sep 15, 2026
Improper authentication in OpenAM before 16.1.1 allows remote authenticated users to mint OAuth tokens as other registered clients. ClientCredentialsReader reuses a ClientJwksResolverCache entry without binding the cached jwks_uri resolver and verified assertion to the expected client ID. Any registered client with published keys, including one created through open dynamic registration when enabled, can impersonate a jwks_uri client across realms in the same process.
Summary
What happened
Improper authentication in OpenAM before 16.1.1 allows remote authenticated users to mint OAuth tokens as other registered clients. ClientCredentialsReader reuses a ClientJwksResolverCache entry without binding the cached jwks_uri resolver and verified assertion to the expected client ID. Any registered client with published keys, including one created through open dynamic registration when enabled, can impersonate a jwks_uri client across realms in the same process.
The record
- CVE
- CVE-2026-47426
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- Open Identity Platform
- Product
- OpenAM
- Classifications
- CWE-287, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 16.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo