CVE-2025-64099: OpenIdentityPlatform OpenAM · Injection
Affects OpenIdentityPlatform OpenAMSource CVE Database V5
Not known to be exploited · CVSS 8.1 High : upgrade to 16.0.0 soon.
Data as of 26 Oct 2026, 15:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 16.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:UExploitation evidence
Disclosed: evidence found.
CVE published 12 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade openidentityplatform/OpenAM to 16.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubopenidentityplatform/OpenAMpkg:github/openidentityplatform/OpenAMOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The primary mitigation is to upgrade all OpenAM deployments to version 16.0.0 or later, where the vulnerability is fixed. Organizations should audit their use of the 'claims_parameter_supported' feature and disable it if not required. Review client applications that consume id_token and user_info claims to ensure they do not blindly trust or rely solely on claims for critical identity decisions, especially fields like email addresses. Implement additional validation and verification mechanisms on the client side to detect anomalous or unexpected claim values. Employ strict input validation and sanitization on any user-controllable parameters related to identity tokens. Monitor logs for unusual authorization requests containing suspicious claims parameters. Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block injection attempts targeting the claims parameter. Conduct penetration testing and code reviews focused on identity token handling and claims processing. Finally, maintain an incident response plan tailored to identity compromise scenarios.
Description
Open Access Management (OpenAM) is an access management solution. In versions prior to 16.0.0, if the "claims_parameter_supported" parameter is activated, it is possible, thanks to the "oidc-claims-extension.groovy" script, to inject the value of one's choice into a claim contained in the id_token or in the user_info. In the request of an authorize function, a claims parameter containing a JSON file can be injected. This JSON file allows attackers to customize the claims returned by the "id_token" and "user_info" files. This allows for a very wide range of vulnerabilities depending on how clients use claims. For example, if some clients rely on an email field to identify a user, an attacker can choose the email address they want, and therefore assume any identity they choose. Version 16.0.0 fixes the issue.