CVE-2026-80322
Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout.
CVSS
—
Sem CVSS
EPSS
—
KEV
—
Exploit Today
—
0-100
Publicado: 17 de nov. de 2026 · Última mod.: 17 de nov. de 2026 · CWE-201 · CWE-226 · CWE-366
Ainda não há histórico EPSS suficiente.
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.
- docs.pingidentity.comhttps://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html
- docs.pingidentity.comhttps://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html
- docs.pingidentity.comhttps://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html
- docs.pingidentity.comhttps://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html
- support.pingidentity.comhttps://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage
- www.pingidentity.comhttps://www.pingidentity.com/en/resources/downloads/pingauthorize.html