CVE-2026-80322: Ping Identity PingAuthorize · Race Condition Within a Thread
Affects Ping Identity PingAuthorizeSource CVE Database V5
Not known to be exploited · CVSS 8.3 High · fixed in 11.1.0.1 : patch Ping Identity PingAuthorize soon.
Data as of 17 Nov 2026, 18:05 UTC
Thin evidence
One scorer or none| CNA (Ping Identity) | CVSS 4.0 | 8.3 |
|---|
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-17.
- Patch
- Available – fixed in 11.1.0.1, 11.0.0.4, 10.3.0.6 +1
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/RE:MExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade Ping Identity PingAuthorize to 11.1.0.1, 11.0.0.4, 10.3.0.6 or 10.2.0.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Ping IdentityPingAuthorize | Affected
| Fixed in
|
| Ping IdentityPingAuthorize | Affected
| Fixed in
|
| Ping IdentityPingAuthorize | Affected
| Fixed in
|
| Ping IdentityPingAuthorize | Affected
| Fixed in
|
AI-suggested
Fixed versions are available: 10.2.0.9, 10.3.0.6, 11.0.0.4, and 11.1.0.1. Users should upgrade to these or later releases to remediate the vulnerability. No other mitigation or temporary workaround is indicated in the available data.
Description
CVE-2026-80322 is a race condition vulnerability in Ping Identity's PingAuthorize component operating in Gateway mode. Under certain conditions, an asynchronous upstream request may continue after the 30-second gateway timeout, causing a late response to be incorrectly sent to a subsequent request. This can lead to unauthorized information disclosure between separate requests. The issue affects multiple versions prior to fixed releases and has a high severity rating.
References
- support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage (opens in a new tab)
- docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html (opens in a new tab)
- pingidentity.com/en/resources/downloads/pingauthorize.html (opens in a new tab)
- docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html (opens in a new tab)
- docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html (opens in a new tab)
- docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html (opens in a new tab)