HighCVE-2026-80322

    Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse (CVE-2026-80322)

    Published Last modified Sources: EUVD, CVE.org

    Share

    What is affected, what to do

    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.

    Update Ping Identity PingAuthorize to version 10.2.0.9, Ping Identity PingAuthorize to version 10.3.0.6, Ping Identity PingAuthorize to version 11.0.0.4.

    Affected
    • Ping Identity PingAuthorize lt *..10.2.0.9
    • Ping Identity PingAuthorize lt 10.3..10.3.0.6
    • Ping Identity PingAuthorize lt 11.0..11.0.0.4
    • Ping Identity PingAuthorize lt 11.1..11.1.0.1
    Fixed in
    • Ping Identity PingAuthorize 10.2.0.9
    • Ping Identity PingAuthorize 10.3.0.6
    • Ping Identity PingAuthorize 11.0.0.4
    • Ping Identity PingAuthorize 11.1.0.1

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.3

    XIEM Effective CVSS

    Highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    8.3

    CVSS v4

    Severity High on the scale from 0 to 10.

    Source: EUVD, CVE.org

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 39.4

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    83.90 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.3 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.3
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    39.4
    High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: none known · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 17 November 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-366, CWE-201, CWE-488, CWE-226, CWE-772

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    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.

    Source: ENISA EUVD, cvelistv5, CVE.org (MITRE), NVD (NIST)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    Ping IdentityPingAuthorize
    • 11.1 – < 11.1.0.1
    • 10.3 – < 10.3.0.6
    • < 10.2.0.9
    • 11.0 – < 11.0.0.4
    • 11.1.0.1
    • 10.3.0.6
    • 10.2.0.9
    • 11.0.0.4

    Vendors and products

    Weakness classes (CWE)

    • CWE-366Race Condition within a Thread

      Base

      If two threads of execution use a resource simultaneously, there exists the possibility that resources may be used while invalid, in turn making the state of execution undefined.

      Entry at MITRE CWE-366
    • CWE-201Insertion of Sensitive Information Into Sent Data

      Base

      The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

      Entry at MITRE CWE-201
    • CWE-488Exposure of Data Element to Wrong Session

      Base

      The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.

      Entry at MITRE CWE-488
    • CWE-226Sensitive Information in Resource Not Removed Before Reuse

      Base

      The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or "zeroize" the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.

      Entry at MITRE CWE-226
    • CWE-772Missing Release of Resource after Effective Lifetime

      Base

      The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

      Entry at MITRE CWE-772

    References & sources

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Receivedpingidentity.com

      Show 14 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      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
      Weakness type (CWE)added
      —
      CWE-201
      Weakness type (CWE)added
      —
      CWE-226
      Weakness type (CWE)added
      —
      CWE-366
      Weakness type (CWE)added
      —
      CWE-488
      Weakness type (CWE)added
      —
      CWE-772
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/80xxx/CVE-2026-80322.json">CVE-2026-80322</a>
      Referenceadded
      —
      https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html
      Referenceadded
      —
      https://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html
      Referenceadded
      —
      https://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html
      Referenceadded
      —
      https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html
      Referenceadded
      —
      https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage
      Referenceadded
      —
      https://www.pingidentity.com/en/resources/downloads/pingauthorize.html

      Source identifier: responsible-disclosure@pingidentity.com

    2. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: none known, automatable: no

      Show the original change
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      SSVC assessmentadded
      —
      {"id":"CVE-2026-80322","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-17T17:56:38.787988Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-80322
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-80322"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-80322.svg?lang=en" alt="CVE-2026-80322 – NEOSEC Intel" height="20"></a>