CVE-2026-80322Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse
- 8.3HighCVSS base score
- 0.45%Exploitation in 30 daysEPSS · top 61% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying keep-alive connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests.
Timeline
ID reserved
By Ping Identity
- 3 months later
· 3 months later
Published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| Ping IdentityCNA (assigner) | 4.0 | High8.3 | 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:M |
| NVDNVD · Received | 4.0 | High8.3 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:M/U:X |
- EPSS (exploitation in 30 days)
- 0.45% · top 61% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.3.
Affected products
- affected < 10.2.0.9
- affected 10.3 – < 10.3.0.6
- affected 11.0 – < 11.0.0.4
- affected 11.1 – < 11.1.0.1
What to do
Solution: Upgrade to PingAuthorize 10.2.0.9, 10.3.0.6, 11.0.0.4, or 11.1.0.1, or a later maintenance release on the same version train. For Docker-based DevOps deployments, refreshed images are available under the edge, latest, and 2609 tags.
Workaround: As a temporary mitigation, disable HTTP keep-alive and connection reuse on any proxies or load balancers positioned in front of the affected PingAuthorize instance. HTTP keep-alive is enabled by default in HTTP/1.1 and later and must be explicitly disabled in the proxy configuration. This workaround does not remove the vulnerability; applying the patch remains the only permanent solution.
References
References6
- https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage (opens in a new tab)vendor-advisory
- https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html (opens in a new tab)release-notes
- https://www.pingidentity.com/en/resources/downloads/pingauthorize.html (opens in a new tab)product
- https://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html (opens in a new tab)release-notes
- https://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html (opens in a new tab)release-notes
- https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html (opens in a new tab)release-notes
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-127135 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-80322)Record last updated .