Quick answers
- Is CVE-2026-21391 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-21391 being exploited in the wild.
- How severe is CVE-2026-21391?
- Informational severity, published 14 September 2026.
- Which products and versions are affected?
- Ping Identity PingAM.
- Is there a fix for CVE-2026-21391?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-21391 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-21391?
- Check whether you run Ping Identity PingAM. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an improper validation issue in PingAM's ID Token claim handling. A well-crafted request can be used to set or override arbitrary or protected claims within an ID Token, circumventing normal authentication controls. In certain configurations, this enables authentication bypass via spoofing, allowing an attacker to impersonate legitimate users or escalate privileges. The attack is likely achievable over the network without authentication preconditions. Patches from Ping Identity are expected through their security advisory channels.
Affected products
- Ping Identity PingAM
Timeline
- 2026-09-14: disclosed