CVE-2026-80322: high-severity vulnerability in PingAuthorize
Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.3epss 0.3%
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.
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
Affected products
Ping Identity · PingAuthorizeReferences
https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.htmlhttps://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.htmlhttps://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.htmlhttps://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.htmlhttps://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakagehttps://www.pingidentity.com/en/resources/downloads/pingauthorize.html