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

CVE-2026-86411: FTP STARTTLS Auth Bypass Vulnerability

CVE-2026-86411 is an authentication bypass flaw in FTP STARTTLS that allows connection reuse without proper re-authentication. This post explains its impact, affected versions, and mitigation steps.

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

CVE-2026-86411 affects the curl library's FTP connection pooling logic. An ftp:// transfer configured with CURLUSESSL_NONE can reuse a pooled FTP control connection that a previous easy handle upgraded with STARTTLS and authenticated using a client certificate. The second handle performs neither a new TLS handshake nor a new FTP login. The server continues to authorize the reused connection under the first handle's certificate identity. This produces a cross-handle authentication confusion that allows an unauthenticated or less-privileged transfer to inherit the credentials of a prior authenticated session.

Critical Impact

A curl easy handle requesting plaintext FTP can silently inherit TLS client-certificate authorization from a pooled connection, bypassing intended authentication boundaries.

Affected Products

  • curl (libcurl) FTP protocol handler
  • Applications that pool libcurl easy handles with mixed CURLUSESSL settings
  • Workflows mixing authenticated FTPS/STARTTLS and plaintext ftp:// transfers

Discovery Timeline

  • 2026-10-20 - CVE-2026-86411 published to the National Vulnerability Database
  • 2026-10-22 - Last updated in NVD database

Technical Details for CVE-2026-86411

Vulnerability Analysis

The vulnerability sits in libcurl's connection reuse decision for FTP transfers. libcurl pools open control connections keyed on host and port characteristics. When a first easy handle upgrades the FTP control channel using STARTTLS (also referred to as AUTH TLS) and completes authentication with a client certificate, the server tracks the authenticated identity on that control connection. A second easy handle configured with CURLUSESSL_NONE reuses the same pooled connection without renegotiating TLS or issuing a new USER/PASS sequence. The reused handle issues FTP commands against a channel that the server still considers authenticated as the first handle's certificate identity.

The result is authentication context carrying across easy handles that were never intended to share credentials. See the curl.se CVE-2026-86411 advisory and the HackerOne Report #3973190 for additional technical detail.

Root Cause

The connection reuse check does not treat the TLS state and FTP authentication state of a pooled control connection as part of the reuse eligibility criteria. A handle requesting CURLUSESSL_NONE should not match a pooled connection that has already been upgraded via STARTTLS and authenticated with a client certificate. The missing invariant allows cross-handle authority inheritance, a form of Broken Access Control arising from improper session state binding.

Attack Vector

Exploitation requires an application that uses libcurl to perform multiple FTP transfers against the same host using differing CURLUSESSL settings within a single process. An attacker who controls or influences a later ftp:// transfer can cause it to reuse an authenticated TLS control connection and issue commands as the prior certificate identity. This is primarily a local or in-process authorization boundary issue rather than a remote network exploit. No verified proof-of-concept code has been published for this issue.

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-86411

Indicators of Compromise

  • FTP server audit logs showing commands executed over a TLS-upgraded control channel without a preceding AUTH TLS or USER handshake for that session
  • Multiple distinct application transfers attributed to the same client-certificate identity when only one such transfer was intended
  • Application logs showing successful ftp:// operations where the configured CURLUSESSL was NONE yet server policy requires certificate authentication

Detection Strategies

  • Inventory applications linking against libcurl and identify any that mix CURLUSESSL_NONE and CURLUSESSL_ALL/CURLUSESSL_CONTROL against the same host within one process
  • Enable verbose libcurl logging (CURLOPT_VERBOSE) in test environments to observe Re-using existing connection messages on FTP control channels
  • Correlate FTP server-side session identifiers with client certificate serial numbers to flag command sequences that lack an explicit authentication phase

Monitoring Recommendations

  • Alert on FTP control sessions where privileged commands (STOR, DELE, RNFR) are issued without a matching AUTH/USER/PASS sequence in the same connection record
  • Track libcurl versions deployed across build pipelines and container images to confirm patch coverage
  • Monitor FTP servers for authenticated sessions that persist across unexpected idle intervals, which may indicate pooled reuse by unrelated handles

How to Mitigate CVE-2026-86411

Immediate Actions Required

  • Upgrade to the fixed libcurl release noted in the curl.se advisory once available in your distribution
  • Audit application code that creates multiple curl easy handles against FTP endpoints to confirm consistent CURLUSESSL settings per host
  • Disable connection reuse for FTP transfers that cross authentication boundaries by setting CURLOPT_FORBID_REUSE on sensitive handles

Patch Information

Refer to the vendor advisory at curl.se CVE-2026-86411 Documentation and the machine-readable curl.se CVE-2026-86411 JSON data for the fixed version range and commit identifiers. Rebuild applications that statically link libcurl once the patched version is adopted.

Workarounds

  • Use separate curl multi handles or separate processes for authenticated FTPS transfers and plaintext FTP transfers
  • Set CURLOPT_FRESH_CONNECT to force a new connection for every FTP transfer where reuse is not strictly required
  • Enforce CURLUSESSL_ALL consistently for all FTP transfers against servers that accept client-certificate authentication, eliminating the mixed-mode condition
bash
# Configuration example: force fresh FTP connections and forbid pool reuse in libcurl
curl_easy_setopt(handle, CURLOPT_FRESH_CONNECT, 1L);
curl_easy_setopt(handle, CURLOPT_FORBID_REUSE, 1L);
curl_easy_setopt(handle, CURLOPT_USE_SSL, CURLUSESSL_ALL);

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.