Technical impact
PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30‑second gateway timeout. If the keep‑alive connection is reused for a new request before the original response arrives, the late response can be written to the newer exchange, causing a caller to receive data intended for a previous request. The effect is unauthorized disclosure of data between separate requests, as described in the advisory.
Affected Systems
Ping Identity PingAuthorize Gateway mode products, all releases, before the introduced patches. The fix is applied in version 10.2.0.9, 10.3.0.6, 11.0.0.4 or 11.1.0.1 and any later maintenance releases on the same version train.
Risk and Exploitability
The CVSS score of 8.3 classifies this as a high‑severity vulnerability. EPSS is not available, and the vulnerability is not listed in CISA KEV, indicating that it may not yet be widely exploited. The likely attack vector involves network traffic through a proxy or load balancer that handles keep‑alive connections. An attacker who can force the reuse of the same underlying TCP connection against a PingAuthorize instance could potentially intercept response data from a previous request and leak it to a subsequent client. The temporary workaround requires disabling HTTP keep‑alive on intermediary proxies or load balancers; however, applying the vendor patch remains the only permanent fix.