Skip to main content
Vulnerability Database/CVE-2026-86415

CVE-2026-86415: libcurl Schannel Auth Bypass Vulnerability

CVE-2026-86415 is an authentication bypass flaw in libcurl affecting Schannel connections. Cached authenticated connections can be reused across origins, bypassing client certificate controls. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

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-86415 Overview

CVE-2026-86415 affects libcurl's connection cache behavior when using the Schannel TLS backend on Windows. The connection cache match function fails to consider the automatic client certificate option when selecting a reusable connection. An already-authenticated Schannel connection can be returned to a transfer that explicitly disabled the auto client certificate option, including transfers that were redirected to a different origin. This defeats a protection the calling code enabled specifically to prevent cross-origin credential reuse. The flaw sits in libcurl's connection reuse logic and impacts applications relying on Schannel for mutual TLS.

Critical Impact

A redirected libcurl transfer can inherit a cached, client-certificate-authenticated Schannel connection, exposing authenticated sessions to unintended origins.

Affected Products

  • libcurl (Schannel TLS backend on Windows)
  • Applications linking libcurl with Schannel enabled
  • Windows-based tools and services that use libcurl for HTTPS with client certificates

Discovery Timeline

  • 2026-10-20 - CVE-2026-86415 published to NVD
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-86415

Vulnerability Analysis

libcurl maintains a connection cache so transfers can reuse established TLS sessions and avoid repeated handshakes. When a transfer begins, libcurl searches the cache for a matching connection using a set of properties such as host, port, and TLS options. The match function in this flaw omits the automatic client certificate selection flag from its comparison. A transfer that explicitly turns off automatic client certificate selection can therefore be assigned a cached connection that was previously established with that option enabled and already authenticated using a client certificate.

The condition is reachable through HTTP redirects. An application starts a transfer to an origin where client certificate authentication is acceptable. The server redirects to a different origin. libcurl, following the redirect, disables auto client certificate selection to prevent the client certificate from being presented to the new origin. The connection cache then returns the earlier authenticated connection anyway, carrying the authenticated TLS session into the new request.

Root Cause

The defect is a missing property comparison in libcurl's connection cache match logic. The automatic client certificate option is a security-relevant selector but is not part of the match key. This is a configuration and design flaw in connection reuse that produces behavior inconsistent with the caller's stated security policy.

Attack Vector

Exploitation requires a server-side redirect that steers an authenticated Schannel transfer to a destination controlled by the attacker. The destination then receives requests over a TLS connection authenticated with the original client certificate identity. The underlying mechanism is cross-origin credential reuse through a connection cache mismatch. Refer to the cURL CVE-2026-86415 Documentation and HackerOne Report #3993870 for the authoritative technical description.

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 Attacks

Detection Methods for CVE-2026-86415

Indicators of Compromise

  • Schannel client-certificate-authenticated requests arriving at unexpected origins after a redirect chain in libcurl-based clients.
  • Server-side telemetry showing a single client certificate identity reused across unrelated hostnames within a short interval.
  • Application logs where a libcurl transfer followed a cross-origin redirect while using Schannel with client certificates.

Detection Strategies

  • Inventory binaries that statically or dynamically link libcurl built with Schannel, and compare installed versions against the fixed release noted in the cURL advisory.
  • Instrument libcurl-based applications to log the final effective URL of redirected transfers alongside the client certificate identity presented.
  • Review web server and reverse proxy logs for client certificate authentication occurring on endpoints that should not accept it.

Monitoring Recommendations

  • Monitor outbound TLS flows from Windows hosts for client certificate presentation to unexpected destinations.
  • Alert on redirect chains that cross origin boundaries in applications configured for mutual TLS.
  • Track libcurl and dependent application versions through software composition analysis to confirm patch coverage.

How to Mitigate CVE-2026-86415

Immediate Actions Required

  • Upgrade libcurl to the patched version listed in the cURL CVE-2026-86415 Documentation across all Windows systems using the Schannel backend.
  • Identify applications that ship their own copy of libcurl and rebuild or update them with the fixed library.
  • Review libcurl-based workflows that follow redirects while presenting client certificates and restrict redirects where feasible.

Patch Information

The cURL project publishes the fix and affected version range in the official advisory. Consult the cURL CVE-2026-86415 JSON Details for machine-readable version data and update all libcurl instances to the fixed release.

Workarounds

  • Disable automatic following of redirects in libcurl transfers that use client certificates by not setting CURLOPT_FOLLOWLOCATION.
  • Use a non-Schannel TLS backend such as OpenSSL where policy allows, since the flaw is specific to the Schannel connection cache path.
  • Isolate client-certificate-authenticated transfers in separate libcurl handles with their own connection cache to prevent cross-transfer reuse.

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.