Loading...
Skip to main content
GeekWala

CVE-2025-64099 — Vulnerability in...

HIGH

OpenAM: Using arbitrary OIDC requested claims values in id_token and user_info is allowed

Published November 12, 2025Updated November 15, 2025Source: osv

Summary

### Summary If the "claims_parameter_supported" parameter is activated, it is possible through the "oidc-claims-extension.groovy" script, to inject the value of choice into a claim contained in the id_token or in the user_info. Authorization function requests do not prevent a claims parameter containing a JSON file to be injected. This JSON file allows users to customize 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, users can choose to entera any email address, and therefore assume any chosen identity.

Advisory Timeline

  • First published November 12, 2025 (334 days ago).
  • Last revised November 15, 2025 — 2 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven
Update org.openidentityplatform.openam:openam-oauth2 to 16.0.3 or later
<!-- Update pom.xml dependency version to 16.0.3 for org.openidentityplatform.openam:openam-oauth2 -->

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: maven (1).

PackageEcosystemAffectedFixed In
org.openidentityplatform.openam:openam-oauth2
maven
14.5.2, 14.5.3, 14.5.4, 14.6.1 (+31 more)16.0.3

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 9.8 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
—
Confidentiality
—
Integrity
—
Availability
—

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:U

References

Frequently Asked Questions

What is CVE-2025-64099?
OpenAM: Using arbitrary OIDC requested claims values in id_token and user_info is allowed This vulnerability has been assigned a severity rating of HIGH (CVSS score: 9.8/10).
How do I check if my project is affected by CVE-2025-64099?
CVE-2025-64099 affects org.openidentityplatform.openam:openam-oauth2. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2025-64099 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
9.8

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-39hr-239p-fhqc

Related CVEs

  • CVE-2026-33439
    CRITICAL

    OpenIdentityPlatform OpenAM: Pre-Authentication Remote Code Execution via `jato.clientSession` Deserialization in OpenAM

  • CVE-2026-45051
    CRITICAL

    OpenAM: Pre-auth RCE via Java Deserialization in WebAuthn Authenticator Storage

  • CVE-2026-44203
    CRITICAL

    OpenAM has pre-auth Reflected XSS in OAuth2 / OIDC response_mode=form_post via state parameter (FormPostResponse.ftl)

  • CVE-2026-62263
    CRITICAL

    OpenAM: WebAuthn Java deserialization RCE via ObjectInputFilter depth>1 bypass

  • CVE-2026-45052
    CRITICAL

    OpenAM Pre-auth User Profile Tampering via Anonymous SOAP Authn in Liberty IDPP/Discovery Endpoints

  • CVE-2026-62379
    CRITICAL

    OpenAM: Unauthenticated Remote Code Execution via Class.forName in AuthXMLUtils.createCustomCallback

  • CVE-2026-45794
    HIGH

    OpenAM has Unsafe Java Deserialization via SNS

  • CVE-2026-45048
    HIGH

    OpenAM Authenticated Privilege Escalation via Raw Token Disclosure Session RPC

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies