Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-86414 Overview
CVE-2026-86414 affects libcurl, the widely deployed URL transfer library maintained by the cURL project. A malicious or compromised HTTP proxy can trick libcurl into leaking the origin server's credentials to the proxy itself. The attack abuses the authentication challenge flow during CONNECT tunnel establishment.
When libcurl issues a CONNECT request to establish a tunnel, a hostile proxy responds with HTTP 401 and a WWW-Authenticate: header instead of the expected HTTP 407 with Proxy-Authenticate:. libcurl treats the challenge as originating from the destination server and sends origin credentials, including Basic passwords or Negotiate/Kerberos tickets, to the proxy.
Critical Impact
Origin-server credentials, including Basic passwords and Kerberos service tickets, can be exfiltrated to any proxy sitting in the TLS tunnel setup path.
Affected Products
- libcurl (HTTP proxy / CONNECT tunnel code paths)
- cURL command-line tool linked against affected libcurl versions
- Applications and runtimes bundling vulnerable libcurl builds
Discovery Timeline
- 2026-10-20 - CVE-2026-86414 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-86414
Vulnerability Analysis
The flaw lives in libcurl's handling of HTTP authentication challenges returned during proxy tunnel negotiation. When a client requests an HTTPS resource through an HTTP proxy, libcurl sends a CONNECT host:port HTTP/1.1 request. A well-behaved proxy that requires authentication answers with HTTP 407 and a Proxy-Authenticate: header. libcurl then responds with the configured proxy credentials.
In this vulnerability, a hostile proxy returns HTTP 401 with WWW-Authenticate: instead. libcurl misinterprets this as a challenge from the origin server behind the tunnel, even though no tunnel has been established. It then transmits the origin credentials, which were intended only for the destination host, directly to the proxy.
The impact depends on the authentication scheme in use. HTTP Basic sends the username and password base64-encoded, giving the proxy full plaintext credentials. Negotiate or Kerberos sends a service ticket that the proxy can replay against the origin service.
Root Cause
The root cause is improper trust-boundary enforcement between proxy-authentication and server-authentication contexts [CWE-287, CWE-522]. libcurl does not require that a WWW-Authenticate: challenge arrive only after a successful CONNECT tunnel. The challenge selector keys off the HTTP status code and header name rather than the connection state.
Attack Vector
An attacker needs control of an HTTP proxy that a victim client is configured to use, or a network position allowing proxy-response injection before TLS is established. The attacker observes the CONNECT request, replies with HTTP/1.1 401 Unauthorized and a crafted WWW-Authenticate: Basic realm="..." or WWW-Authenticate: Negotiate header, and captures the credential material libcurl sends in the follow-up request. Full technical details are documented in the cURL CVE-2026-86414 Advisory and HackerOne Report #3993566.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-86414
Indicators of Compromise
- HTTP 401 responses returned to a CONNECT request on proxy connections, instead of the expected 407 status.
- Outbound Authorization: Basic or Authorization: Negotiate headers sent on the same TCP connection where a CONNECT tunnel was never confirmed with a 200 response.
- Unexpected Kerberos service-ticket requests from client workstations for origin-service SPNs tied to tunneled destinations.
Detection Strategies
- Inspect proxy and network telemetry for the pattern: client sends CONNECT, proxy returns 401, client immediately retries with Authorization: on the same socket.
- Alert on libcurl or cURL user agents sending credentials to intermediaries that are not the declared origin host.
- Correlate credential-use events in identity logs with proxy session logs to identify replayed tickets.
Monitoring Recommendations
- Enable proxy access logging that records request method, response code, and authentication headers at the proxy edge.
- Track libcurl versions deployed across workstations, servers, and container images through software inventory tooling.
- Monitor Kerberos ticket issuance for anomalous service principal names originating from endpoints running HTTP client workloads.
How to Mitigate CVE-2026-86414
Immediate Actions Required
- Inventory all systems, containers, and applications linking against libcurl and identify versions in scope per the vendor advisory.
- Upgrade libcurl to the fixed release referenced in the cURL CVE-2026-86414 Advisory as soon as the patched version is available in your distribution channels.
- Rotate any origin-service credentials that may have transited untrusted proxies during the exposure window.
Patch Information
The cURL project tracks fix details in the CVE-2026-86414 JSON Details and the cURL CVE-2026-86414 Advisory. Apply the vendor patch through operating-system package updates, container base-image rebuilds, and language-runtime updates that bundle libcurl.
Workarounds
- Avoid passing origin credentials to libcurl when traffic traverses untrusted HTTP proxies; use client certificates or bearer tokens delivered inside the TLS tunnel instead.
- Restrict outbound proxy use to vetted, authenticated proxies under administrative control.
- Disable Negotiate and Basic authentication in libcurl invocations that must transit proxies, using explicit --anyauth restrictions or scheme-specific flags per the cURL documentation.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

