Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse
Summary
| CVE | CVE-2026-80322 |
|---|---|
| State | PUBLISHED |
| Assigner | Ping Identity |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-11-17 18:17:58 UTC |
| Updated | 2026-11-17 18:17:58 UTC |
| 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. |
Risk And Classification
Primary CVSS: v4.0 8.3 HIGH from [email protected]
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
Problem Types: CWE-201 | CWE-226 | CWE-366 | CWE-488 | CWE-772 | CWE-366 CWE-366 Race condition within a thread | CWE-201 CWE-201 Insertion of sensitive information into sent data | CWE-488 CWE-488 Exposure of data element to wrong session | CWE-226 CWE-226 Sensitive information in resource not removed before reuse | CWE-772 CWE-772 Missing release of resource after effective lifetime
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 4.0 | [email protected] | Secondary | 8.3 | HIGH | 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/C... |
| 4.0 | CNA | CVSS | 8.3 | HIGH | 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 |
CVSS v4.0 Breakdown
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
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Ping Identity | PingAuthorize | affected 10.2.0.9 custom | Not specified |
| CNA | Ping Identity | PingAuthorize | affected 10.3 10.3.0.6 custom | Not specified |
| CNA | Ping Identity | PingAuthorize | affected 11.0 11.0.0.4 custom | Not specified |
| CNA | Ping Identity | PingAuthorize | affected 11.1 11.1.0.1 custom | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| www.pingidentity.com/en/resources/downloads/pingauthorize.html | [email protected] | www.pingidentity.com | |
| support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage | [email protected] | support.pingidentity.com | |
| docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_hom... | [email protected] | docs.pingidentity.com | |
| docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_hom... | [email protected] | docs.pingidentity.com | |
| docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_hom... | [email protected] | docs.pingidentity.com | |
| docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_hom... | [email protected] | docs.pingidentity.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
Additional Advisory Data
Solutions
CNA: Upgrade to PingAuthorize 10.2.0.9, 10.3.0.6, 11.0.0.4, or 11.1.0.1, or a later maintenance release on the same version train. For Docker-based DevOps deployments, refreshed images are available under the edge, latest, and 2609 tags.
Workarounds
CNA: As a temporary mitigation, disable HTTP keep-alive and connection reuse on any proxies or load balancers positioned in front of the affected PingAuthorize instance. HTTP keep-alive is enabled by default in HTTP/1.1 and later and must be explicitly disabled in the proxy configuration. This workaround does not remove the vulnerability; applying the patch remains the only permanent solution.