HIGH 8.3 NVD
CVE-2026-80322
Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying ke
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.
References
- https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_ho
- https://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_ho
- https://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_ho
- https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_ho
- https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-
This high severity vulnerability with a CVSS score of 8.3 was published on 2026-11-17 via NVD.
vulnfeed aggregates 21154 vulnerabilities from NVD, CISA KEV,
Ubuntu, Debian, Red Hat, Kubernetes, Exploit-DB, OSS-Security, GitHub and OpenStack — updated every 4 hours.