CVE-2025-64099 OpenAM allows use of arbitrary OIDC requested claims values in id_token and user_info
Attackers can inject arbitrary claims into OIDC tokens when claims support is enabled, allowing them to impersonate users and bypass authentication.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-64099?
CVE-2025-64099 is a high-severity authentication bypass vulnerability in OpenIdentityPlatform OpenAM, published on 12 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-74
Which versions are affected by CVE-2025-64099?
2 open source packages ship an affected version, including org.openidentityplatform.openam:openam-oauth2.
| Package | Affected | Fixed in |
|---|---|---|
org.openidentityplatform.openam:openam-oauth2 Maven | All versions | 16.0.3 |
org.openidentityplatform.openam:openam-oauth2 Maven | All versions | 16.0.3 |
How do I fix CVE-2025-64099?
Upgrade org.openidentityplatform.openam:openam-oauth2 to 16.0.3 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2025-64099 being exploited?
There is no known exploitation of CVE-2025-64099 in the wild and no public exploit code.
Sources
Also known as GHSA-39hr-239p-fhqc.