Identity impersonation via unchecked requested OIDC claims
Published Nov 12, 2025 · Updated Nov 12, 2025
OIDC claim injection in Open Identity Platform OpenAM before 16.0.0 allows remote attackers to assume identities via crafted authorization requests. The oidc-claims-extension.groovy attributeRetriever returned a sole requested claim value without checking it against the authenticated identity's stored attribute. Exploitation requires claims_parameter_supported to be enabled and a client to trust the attacker-controlled claim, such as an email address, for identity decisions.
Summary
What happened
OIDC claim injection in Open Identity Platform OpenAM before 16.0.0 allows remote attackers to assume identities via crafted authorization requests. The oidc-claims-extension.groovy attributeRetriever returned a sole requested claim value without checking it against the authenticated identity's stored attribute. Exploitation requires claims_parameter_supported to be enabled and a client to trust the attacker-controlled claim, such as an email address, for identity decisions.
The record
- CVE
- CVE-2025-64099
- Published
- Nov 12, 2025
- Updated
- Nov 12, 2025
- Vendor
- Open Identity Platform
- Product
- OpenAM
- Classifications
- CWE-74, T1606
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- Nov 12, 2025Record 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.0.0
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