cbcvebase.
CVE-2026-11856
published 2026-07-03

CVE-2026-11856: Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one…

PriorityP358critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.69%
51.0th percentile
Successfully using libcurl to do a transfer to a specific HTTP origin (`hostA`) with **Digest** authentication and then changing the origin to a different one (`hostB`) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the `Authorization:` header field meant for `hostA`, to `hostB`.

Affected

179 ranges· showing 25
VendorProductVersion rangeFixed in
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——
curlcurl——

Detection & IOCsextracted from sources · hover to see the quote

  • →Detect HTTP requests where an Authorization header using Digest authentication scheme is sent to a different host/origin than the one for which it was originally issued — indicative of libcurl handle reuse leaking auth state across origins. ↗
  • →Only libcurl-based applications are affected (not the curl CLI). Focus detection and auditing on applications that use libcurl's easy handle API and reuse handles across different HTTP origins with Digest authentication. ↗
  • →Flag application code patterns where a single libcurl easy handle is reused for transfers to different HTTP origins while Digest auth state may be attached, without calling curl_easy_cleanup() and curl_easy_init() between requests. ↗
  • ·Vulnerability only affects libcurl versions 7.10.6 through 8.20.0 inclusive; fixed in 8.21.0. Audit deployed libcurl versions to scope exposure. ↗
  • ·The curl CLI tool is NOT affected; only applications using the libcurl C library API are vulnerable. Detections should be scoped accordingly. ↗
  • ·The flaw leaks the Authorization HTTP header (Digest auth state) to an unintended origin — credentials themselves are not directly leaked, but the authenticated session header is. ↗
  • ·Red Hat has deferred fixes for RHEL 6, 7, 8, 9, 10 and RHCOS/OpenShift 4. Red Hat Hardened Images remain affected. No mitigation is currently available from Red Hat; the recommended workaround is to create a fresh handle per origin. ↗

CVSS provenance

nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vendor_redhat9.8CRITICAL
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.