CVE-2026-80322
Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout.
Impact
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.
An attacker can exploit this over the network, without logging in, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: high risk of data being read, low risk of data or systems being changed.
Affected products · Ping Identity
| Product | Affected versions |
|---|---|
| PingAuthorize | before 10.2.0.9 from 10.3 before 10.3.0.6 from 11.0 before 11.0.0.4 from 11.1 before 11.1.0.1 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage
- https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html
- https://www.pingidentity.com/en/resources/downloads/pingauthorize.html
- https://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html
- https://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html
- https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html
- https://github.com/advisories/GHSA-cr89-8f7q-v4r4
- https://nvd.nist.gov/vuln/detail/CVE-2026-80322