{
  "id": "CVE-2026-80322",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-80322",
  "published_at": "2026-11-17T17:44:48.866Z",
  "title": "Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse",
  "vendor": "Ping Identity",
  "product": "PingAuthorize",
  "cvss": {
    "score": 8.3,
    "source": "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-366",
  "cvss_by_source": {
    "cna": 8.3
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Ping Identity",
        "product": "PingAuthorize",
        "ranges": [
          "\u003c 10.2.0.9",
          "\u003e= 10.3, \u003c 10.3.0.6",
          "\u003e= 11.0, \u003c 11.0.0.4",
          "\u003e= 11.1, \u003c 11.1.0.1"
        ],
        "fixed_in": [
          "10.2.0.9",
          "10.3.0.6",
          "11.0.0.4",
          "11.1.0.1"
        ]
      }
    ],
    "solutions": [
      "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."
    ],
    "upgrade": [
      "Upgrade PingAuthorize to 10.2.0.9 or 10.3.0.6 or 11.0.0.4 or 11.1.0.1 or later."
    ],
    "workarounds": [
      "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."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage"
      },
      {
        "kind": "Release notes",
        "url": "https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html"
      },
      {
        "kind": "Release notes",
        "url": "https://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html"
      },
      {
        "kind": "Release notes",
        "url": "https://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html"
      },
      {
        "kind": "Release notes",
        "url": "https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
