CVE-2026-80322

8.3High

Published 17 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

8.3CVSS

High

0CVSS v4.010

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
High impact on confidentiality
Weakness
CWE-201, CWE-226, CWE-366, CWE-488, CWE-772

What an attacker gets

Remote attackers can cause unauthorized information disclosure by triggering a cross-request response leak. This occurs when an asynchronous upstream request returns after a timeout and is incorrectly mapped to a subsequent request on a reused connection.

Root cause

The gateway fails to properly discard or isolate late responses from asynchronous upstream requests after the 30-second timeout threshold.

Affected versions

All releases of PingAuthorize in Gateway mode.

CVSS v4.0 · 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

Fix & remediation

Upgrade to the latest version of PingAuthorize provided by Ping Identity, as specified in security advisory SECADV057. If you cannot upgrade immediately, contact Ping Identity support to discuss specific configuration changes to mitigate connection reuse behavior.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-80322