Skip to main content
VulnerabilityPublished

CVE-2026-80322: Under specific conditions, PingAuthorize

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-80322· High 8.3

Not known to be exploited · CVSS 8.3 High · fixed in 11.1.0.1 : patch PingAuthorize soon.

Data as of 17 Nov 2026, 19:50 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Ping Identity)CVSS 4.08.3
Patch
Available – fixed in 11.1.0.1, 11.0.0.4, 10.3.0.6 +1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade PingAuthorize to 11.1.0.1, 11.0.0.4, 10.3.0.6 or 10.2.0.9.

Affected software

ProductAffectedFixed in
Ping IdentityPingAuthorizeAffected
  • >=11.1 <11.1.0.1
Fixed in
  • 11.1.0.1
Ping IdentityPingAuthorizeAffected
  • >=11.0 <11.0.0.4
Fixed in
  • 11.0.0.4
Ping IdentityPingAuthorizeAffected
  • >=10.3 <10.3.0.6
Fixed in
  • 10.3.0.6
Ping IdentityPingAuthorizeAffected
  • <10.2.0.9
Fixed in
  • 10.2.0.9

AI-suggested

If you cannot patch yet, users should consider mitigating risk by disabling keep-alive connections if feasible or limiting gateway timeout settings, though these are not confirmed mitigations.

Description

CVE-2026-80322 is a vulnerability in PingAuthorize operating in Gateway mode where asynchronous upstream requests can continue after a 30-second timeout. If the underlying keep-alive connection is reused before the original response arrives, the late response may be sent to a different request, risking unauthorized information disclosure between separate requests.

References

Community reviews

Loading reviews…