CVE-2026-80322

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

Published Nov 17, 2026 CVSS 4.0 · 8.3 High EPSS n/a KEV · Not listed
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.

Analysis

AI-generated

Technical impact

PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30‑second gateway timeout. If the keep‑alive connection is reused for a new request before the original response arrives, the late response can be written to the newer exchange, causing a caller to receive data intended for a previous request. The effect is unauthorized disclosure of data between separate requests, as described in the advisory.

Affected Systems

Ping Identity PingAuthorize Gateway mode products, all releases, before the introduced patches. The fix is applied in version 10.2.0.9, 10.3.0.6, 11.0.0.4 or 11.1.0.1 and any later maintenance releases on the same version train.

Risk and Exploitability

The CVSS score of 8.3 classifies this as a high‑severity vulnerability. EPSS is not available, and the vulnerability is not listed in CISA KEV, indicating that it may not yet be widely exploited. The likely attack vector involves network traffic through a proxy or load balancer that handles keep‑alive connections. An attacker who can force the reuse of the same underlying TCP connection against a PingAuthorize instance could potentially intercept response data from a previous request and leak it to a subsequent client. The temporary workaround requires disabling HTTP keep‑alive on intermediary proxies or load balancers; however, applying the vendor patch remains the only permanent fix.

Remediation

Vendor Solution

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.


Vendor Workaround

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.


OpenCVE Recommended Actions

  • Upgrade PingAuthorize to any patched release (10.2.0.9, 10.3.0.6, 11.0.0.4, 11.1.0.1 or later).
  • If upgrade is not immediately possible, configure proxies or load balancers in front of PingAuthorize to disable HTTP keep‑alive and connection reuse.
  • Monitor vendor advisories for newer releases and apply updates promptly.
  • For Docker deployments, pull updated images from the edge, latest, or 2609 tags to replace older images.

Generated by OpenCVE AI on November 17, 2026 at 19:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
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.
Title Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse
Weaknesses CWE-201
CWE-226
CWE-366
CWE-488
CWE-772
References
Metrics cvssV4_0

{'score': 8.3, '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'}

Subscriptions

No data.

Weaknesses
  • 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

Sources

Status
PUBLISHED
Assigner
Ping Identity
Published
Updated
Nov 17, 2026, 5:57 PM
Reserved
Aug 26, 2026, 8:38 AM
Status
Received
Published
Nov 17, 2026, 6:17 PM
Modified
Nov 17, 2026, 6:17 PM