CVE-2026-80322 · Ping Identity / PingAuthorize
CVE-2026-80322 · Reported 17 Nov 2026
Full advisory details, affected packages, severity context, and original source.
Affected technology
Affected versions and fixes
Version information comes from OSV, NVD, and the CVE vendor record. Each source may describe a different package, release branch, or platform.
Ping Identity / PingAuthorize · custom
CVE vendor record- affected: All earlier versions · before 10.2.0.9 (exclusive) · custom
- affected: From 10.3 (inclusive) · before 10.3.0.6 (exclusive) · custom
- affected: From 11.0 (inclusive) · before 11.0.0.4 (exclusive) · custom
- affected: From 11.1 (inclusive) · before 11.1.0.1 (exclusive) · custom
Fixed releases / commits: Not explicitly provided by this source. Check the vendor guidance.
Other versions: unaffected according to the vendor record.
Advisory overview
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.
Related references
- https://docs.pingidentity.com/pingauthorize/10.2/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/11.0/release_notes/paz_release_notes_legacy_home.html
- https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html
- https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage
- https://www.pingidentity.com/en/resources/downloads/pingauthorize.html
