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.
Published: 2026-11-17
Score: 8.3 High
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Analysis and contextual insights are available on OpenCVE Cloud.

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.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 17 Nov 2026 18:00:00 +0000

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.

cve-icon MITRE

Status: PUBLISHED

Assigner: Ping Identity

Published:

Updated: 2026-11-17T17:57:19.769Z

Reserved: 2026-08-26T08:38:07.043Z

Link: CVE-2026-80322

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-17T18:17:58.950

Modified: 2026-11-17T18:17:58.950

Link: CVE-2026-80322

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-17T19:45:03Z

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