Critical auth-bypass in widely deployed enterprise SSO (PingAM) enabling impersonation and privilege escalation; high-impact for organizations using centralized identity.
CVE-2026-21391
PingAM token-validation flaw allows claim spoofing to bypass authentication.
Is CVE-2026-21391 being exploited?
Not confirmed. CVE-2026-21391 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.
How severe is CVE-2026-21391?
CVE-2026-21391 is rated Critical with a CVSS score of 9.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-21391?
Not known from our data. No patch reference has been recorded for CVE-2026-21391, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-21391 affect?
CVE-2026-21391 affects PingIdentity PingAM (Ping Access/AM identity platform). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-21391?
Apply vendor mitigations/patches immediately; revoke tokens and rotate credentials.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can set/override ID token claims to impersonate users, bypass auth, and escalate privileges for unauthorized access.
Immediate action required
- affected8.1.0
- affected>= 8.0.0 and <= 8.0.2
- affected>= 7.5.0 and <= 7.5.2
- affected>= 7.4.0 and <= 7.4.2
- affected>= 7.3.0 and <= 7.3.3
- affected>= 7.2.0 and <= 7.2.2
- affected>= 7.1.0 and <= 7.1.4
- affected>= 7.0.0 and <= 7.0.2
- affected< 7.0.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.