cve.bz

CVE-2026-80322 Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse

8.3 high

High (8.3) in ping identity pingauthorize.

On this page
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.

Severity

CVSS 4.0

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
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-201 Insertion of Sensitive Information Into Sent Data
CWE-226 Sensitive Information in Resource Not Removed Before Reuse
CWE-366 Race Condition within a Thread
CWE-488 Exposure of Data Element to Wrong Session
CWE-772 Missing Release of Resource after Effective Lifetime
OWASP Top 10
A01:2025 Broken Access Control
Published
Assigned by
Ping Identity (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-80322 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80322?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80322?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80322 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • ping identity:pingauthorize

Versions

From the CNA's record in the CVE List.

ProductAffected
Ping Identity PingAuthorizebefore 10.2.0.9
Ping Identity PingAuthorizefrom 10.3 before 10.3.0.6
Ping Identity PingAuthorizefrom 11.0 before 11.0.0.4
Ping Identity PingAuthorizefrom 11.1 before 11.1.0.1

Attack patterns (CAPEC)

  • CAPEC-37 Retrieve Embedded Sensitive Data Likelihood: High · Severity: Very High
  • CAPEC-469 HTTP DoS Severity: Low
  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High
  • CAPEC-59 Session Credential Falsification through Prediction Likelihood: High · Severity: High
  • CAPEC-60 Reusing Session IDs (aka Session Replay) Likelihood: High · Severity: High
  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-217 Exploiting Incorrectly Configured SSL/TLS Likelihood: Low
  • CAPEC-612 WiFi MAC Address Tracking Severity: Low
  • CAPEC-613 WiFi SSID Tracking Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-201.

References

Check your stackJSON