Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-21391 – Authentication Bypass / ID Token Claim Spoofing – PingAM (all versions prior to 8.1

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-21391 is a critical improper-validation vulnerability in the OIDC Provider component of Ping Identity’s PingAM access management platform. A crafted OIDC request can set or override ID Token claims that should be protected, which in certain configurations can bypass authentication controls and enable impersonation or privilege escalation. The vulnerability has a CVSS v4.0 base score of 9.5 (Critical) and is remotely exploitable over the network.

Technical details

  • Root cause: The PingAM OIDC Provider does not properly validate/restrict which ID Token claims a client can set or override in a request, classified as CWE-290 (Authentication Bypass by Spoofing).
  • Trigger conditions: An attacker sends a specially crafted OIDC authorization/token request that includes arbitrary or protected claims; exploitability depends on the specific OIDC client/relying-party configuration in the deployment.
  • Attack vector: Network-based, requiring no privileges and no user interaction, but requiring certain application-layer configuration conditions to be met (per the CVSS AT:P/AC:L metrics).
  • Impact: Successful exploitation can spoof identity claims within the issued ID Token, allowing authentication bypass, impersonation of other users, and privilege escalation in affected relying-party configurations.

Affected software

  • PingAM 8.1.0
  • PingAM 8.0.0 through 8.0.2
  • PingAM 7.5.0 through 7.5.2
  • PingAM 7.4.0 through 7.4.2
  • PingAM 7.3.0 through 7.3.3
  • PingAM 7.2.0 through 7.2.2
  • PingAM 7.1.0 through 7.1.4
  • PingAM 7.0.0 through 7.0.2
  • All PingAM versions prior to 7.0.0

Severity

  • CVSS v4.0 Base Score: 9.5 (Critical)
  • Vector: 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
  • CWE: CWE-290 (Authentication Bypass by Spoofing)

Mitigation and recommended actions

  • Immediate: Apply the fix published by Ping Identity in Security Advisory 202603 and upgrade to the patched PingAM release referenced in that advisory. Consult the Ping Identity Knowledge Base advisory for the exact build/patch identifier applicable to your deployment track.
  • If no patch is available yet: Review OIDC relying-party (client) configurations to ensure ID Token claims are validated and cannot be overridden by client-supplied input; restrict which claims registered clients are permitted to request or set; monitor OIDC token issuance and authentication logs for anomalous claim values or unexpected privilege grants; limit network exposure of the OIDC Provider endpoints to trusted networks where possible until patched.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge