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

CVE-2026-8927: When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication…

PriorityP357critical9.1CVSS 3.1
AVNACLPRNUINSUCHIHAN
EPSS
0.50%
40.7th percentile
When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against `proxyA` using Digest auth, a subsequent transfer routed through `proxyB` erroneously leaks the `Proxy-Authorization:` header intended solely for `proxyA`.

Affected

174 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 unintended Proxy-Authorization header leakage in libcurl by monitoring for Proxy-Authorization headers being sent to a proxy that differs from the one originally authenticated against, particularly in sequential transfers reusing the same libcurl handle. ↗
  • →Focus detection on libcurl handle reuse patterns where environment-variable proxy configuration (e.g., http_proxy, https_proxy) is used across sequential transfers — the auth state is not cleared between requests, leading to header leakage. ↗
  • →Monitor network traffic for Proxy-Authorization: Digest headers being sent to unexpected or secondary proxy endpoints, which may indicate exploitation of this flaw in environments with multiple proxy configurations. ↗
  • →Audit affected packages in Red Hat environments: curl (Red Hat Hardened Images), rust (Red Hat Hardened Images), libcurl-1.dll and libcurl.so (Red Hat JBoss Core Services) are confirmed affected and should be prioritized for patching and monitoring. ↗
  • ·dotnet8.0 on Red Hat Enterprise Linux 8 is confirmed NOT affected by this CVE and should not be prioritized for remediation. ↗
  • ·No mitigation is currently available that meets Red Hat Product Security criteria; patching is the only viable remediation path. ↗
  • ·The vulnerability only impacts confidentiality (credential leakage via Proxy-Authorization header); no integrity impact has been observed. ↗
  • ·The flaw is specifically triggered by environment-variable-driven proxy configuration (e.g., http_proxy/https_proxy env vars), not by programmatically set proxy options in libcurl. ↗
  • ·The davix package (EPEL) is also tracked for this CVE; community package maintainers must independently verify if the flaw affects their build before updating. ↗

CVSS provenance

nvdv3.19.1CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
vendor_redhat9.1CRITICAL
vendor_ubuntu8.1HIGH
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.