Skip to content
Fencer Intel
high 8.3

CVE-2026-80322 json

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

published 17h ago modified 17h ago also EUVD-2026-127135

cvss
8.3
version 4.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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.

Patch / fix

  • Ping Identity PingAuthorize 10.2.0.9, 10.3.0.6, 11.0.0.4, 11.1.0.1

Is CVE-2026-80322 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
17h ago

CVSS scores

assigned by version score vector
CNA 4.0 8.3 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
CNA 4.0 8.3 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

Affected products

  • Ping Identity PingAuthorize

Classification

Weakness
  • CWE-366 Race Condition within a Thread
  • CWE-201 Insertion of Sensitive Information Into Sent Data
  • CWE-488 Exposure of Data Element to Wrong Session
  • CWE-226 Sensitive Information in Resource Not Removed Before Reuse
  • CWE-772 Missing Release of Resource after Effective Lifetime

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.