EUVD-2026-77425
GHSA-cvq5-qf5h-v345
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach PingAM OIDC token endpoint
-
DeliveryCraft request overriding protected ID Token claims
-
ExploitIssuer emits token with spoofed identity/role
-
ExecutionRelying party trusts forged claims
-
ImpactImpersonate user or escalate privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Anti-spoofing controls
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a PingAM deployment acting as an OpenID Connect / ID Token issuer in a vulnerable configuration ('in certain configurations,' reflected by CVSS AT:P attack requirements), where the token-issuance path lets a crafted request set or override arbitrary or protected ID Token claims. It is network-reachable and unauthenticated (AV:N/PR:N/UI:N) with low attack complexity, but the specific claim-handling/OIDC configuration is the gating factor and success depends on relying parties trusting the forged claims for authentication or authorization; SSVC marks it not automatable, so it is not a mass-scannable default-config exploit. |
| Impact | This is a genuine high-priority issue but the raw 9.5 CVSS 4.0 score slightly overstates trivial exploitability. The vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N shows network, unauthenticated reach with high vulnerable- and subsequent-system confidentiality/integrity impact (VC:H/VI:H/SC:H/SI:H), consistent with token forgery affecting downstream systems - but AT:P (attack requirements present) and the description's 'in certain configurations' qualifier mean exploitation depends on specific PingAM/OIDC configuration, not every default deployment. CISA SSVC reinforces caution: Exploitation is 'none' (no observed or public exploitation), Automatable 'no', but Technical Impact 'total', so a successful attack fully compromises identity integrity. EPSS and KEV are not provided in the input; combined with SSVC exploitation=none, this reads as a serious-but-not-yet-exploited flaw that warrants prompt patching given the identity-provider blast radius, rather than emergency same-day response. |
| Exploit ScenarioDerived | An attacker sends a well-crafted authentication/token request to a vulnerable PingAM OIDC endpoint that injects or overrides a protected ID Token claim - for example setting the subject or a privileged role claim to that of an administrator. The relying-party application trusts the resulting token and grants the attacker the impersonated identity's access, achieving privilege escalation. No public exploit is identified at time of analysis, and CVSS AT:P indicates a specific configuration prerequisite must be met. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 15, 2026
Authentication bypass via ID Token claim spoofing in Ping Identity PingAM allows a remote attacker to inject or override protected ID Token claims through a well-crafted request. In vulnerable configurations this lets an attacker impersonate other identities or escalate privileges by forging trusted claims that downstream relying parties consume. Ping Identity has released a patch; no public exploit is identified at time of analysis, and CISA SSVC records exploitation status as none.
RemediationAI
Apply the Ping Identity fix per the vendor advisory (PingAM Security Advisory 202603, https://support.pingidentity.com/s/article/PingAM-Security-Advisory-202603); a patch is available from the vendor, though exact fixed build numbers per branch are not enumerated in the provided data and should be taken directly from that advisory for your specific 7.0.x-8.1.0 branch. Because the flaw is exploitable only 'in certain configurations,' review OIDC/ID Token issuance settings - audit any custom claim scripts, mappers, or claim-provider plugins that populate ID Token claims and remove client-influenced input paths into protected claims. As compensating controls until patched, restrict and monitor the token/authorization endpoints, tighten which claims relying parties trust from PingAM, and enable logging/alerting on anomalous claim values (unexpected subject, role, or group claims); note these do not fully close the spoofing path and add operational overhead. Cite exact fixed versions from the advisory rather than inferring them.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
PingAM (formerly ForgeRock Access Management) is an enterprise OpenID Connect / OAuth 2.0 and SAML identity provider that issues ID Tokens and access tokens consumed by relying-party applications for authentication and authorization decisions. The root cause is CWE-290 (Authentication Bypass by Spoofing): the OIDC token-issuance path performs improper validation of claim data, so a well-crafted request can set or override arbitrary or normally protected ID Token claims (for example subject, roles, group, or authentication-context claims). Because relying parties trust the identity provider's signed token contents, forged claims propagate as authoritative identity assertions. The affected component is cpe:2.3:a:ping_identity:pingam across multiple 7.x, 8.0.x and 8.1.0 branches.
Know when Pingam gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:N
Network unauthenticated token forgery gated by a specific configuration (AC:H); scope changes to relying parties (S:C) with high identity confidentiality/integrity impact and low availability effect.
Primary rating from Vendor (Ping Identity).
CVSS VectorVendor: Ping Identity
Lifecycle Timeline
2DescriptionCVE.org
An improper validation vulnerability exists within PingAM where a well-crafted request allows arbitrary or protected ID Token claims to be set or overridden. In certain configurations this could allow an attacker to bypass authentication controls via spoofing leading to privilege escalation or impersonation.
Executive ViewAI
Ping Identity PingAM contains a critical authentication bypass vulnerability that allows remote attackers to forge ID token claims, enabling account impersonation and privilege escalation across dependent applications. This directly undermines the identity trust layer for all organizations using PingAM for authentication and single sign-on, compromising the security posture of every downstream system and user.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Exploit-DB