CVE-2026-80322
Under specific conditions, PingAuthorize in Gateway mode can …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html
- docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html
- docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html
- docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html
- support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage
- www.pingidentity.com/en/resources/downloads/pingauthorize.html
- nvd.nist.gov/vuln/detail/CVE-2026-80322
- cve.org/CVERecord?id=CVE-2026-80322
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.