CVE-2026-11586 (GCVE-0-2026-11586)

Vulnerability from cvelistv5 – Published: 2026-07-03 06:13 – Updated: 2026-07-03 06:13
VLAI?
Title
WS Auto-PONG memory exhaustion
Summary
By default, curl automatically responds to WebSocket PING frames. Because curl lacks an upper bound on memory allocation for unacknowledged frames, a malicious server can exhaust all available memory by flooding curl with rapid, sequential PING messages.
Severity ?
No CVSS data available.
CWE
Assigner
References
Impacted products
Vendor Product Version
curl curl Affected: 8.20.0 , ≤ 8.20.0 (semver)
Affected: 8.19.0 , ≤ 8.19.0 (semver)
Affected: 8.18.0 , ≤ 8.18.0 (semver)
Affected: 8.17.0 , ≤ 8.17.0 (semver)
Affected: 8.16.0 , ≤ 8.16.0 (semver)
Create a notification for this product.
Credits
evergarden1123 on hackerone (AntAISecurityLab) Stefan Eissing
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "curl",
          "vendor": "curl",
          "versions": [
            {
              "lessThanOrEqual": "8.20.0",
              "status": "affected",
              "version": "8.20.0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "8.19.0",
              "status": "affected",
              "version": "8.19.0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "8.18.0",
              "status": "affected",
              "version": "8.18.0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "8.17.0",
              "status": "affected",
              "version": "8.17.0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "8.16.0",
              "status": "affected",
              "version": "8.16.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "evergarden1123 on hackerone (AntAISecurityLab)"
        },
        {
          "lang": "en",
          "type": "remediation developer",
          "value": "Stefan Eissing"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "By default, curl automatically responds to WebSocket PING frames. Because curl\nlacks an upper bound on memory allocation for unacknowledged frames, a\nmalicious server can exhaust all available memory by flooding curl with rapid,\nsequential PING messages."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "CWE-770 Allocation of Resources Without Limits or Throttling",
              "lang": "en"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-07-03T06:13:04.448Z",
        "orgId": "2499f714-1537-4658-8207-48ae4bb9eae9",
        "shortName": "curl"
      },
      "references": [
        {
          "name": "json",
          "url": "https://curl.se/docs/CVE-2026-11586.json"
        },
        {
          "name": "www",
          "url": "https://curl.se/docs/CVE-2026-11586.html"
        },
        {
          "name": "issue",
          "url": "https://hackerone.com/reports/3788931"
        }
      ],
      "title": "WS Auto-PONG memory exhaustion"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "2499f714-1537-4658-8207-48ae4bb9eae9",
    "assignerShortName": "curl",
    "cveId": "CVE-2026-11586",
    "datePublished": "2026-07-03T06:13:04.448Z",
    "dateReserved": "2026-06-08T12:17:42.037Z",
    "dateUpdated": "2026-07-03T06:13:04.448Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.