VYPR
Vypr IntelligenceAI-generatedOct 20, 2026· 24 CVEs

Curl: 23 Vulnerabilities Disclosed Together in Single Batch, Exposing Credential and Auth Flaws

Curl project discloses 23 vulnerabilities in a single batch, impacting credential security, authentication, and data integrity across numerous protocols.

Key findings

  • 23 vulnerabilities disclosed in curl and libcurl on October 20, 2026, within a single hour.
  • Flaws include credential leaks, authentication bypasses, and denial-of-service conditions across multiple protocols.
  • Vulnerabilities affect cookie handling, HSTS implementation, and various authentication mechanisms like Negotiate and AWS SigV4.
  • Issues also found in TFTP, FTP, IMAP, POP3, SMTP, SSH, and WebSocket handling.
  • Prompt updates to curl and libcurl are essential for mitigating these widespread risks.

On October 20, 2026, the curl project disclosed a significant batch of 23 vulnerabilities affecting its widely-used data transfer tool and its underlying library, libcurl. These vulnerabilities, all disclosed within a one-hour window, span a range of issues including credential leaks, authentication bypasses, denial-of-service conditions, and protocol-specific flaws. The sheer volume and diversity of these issues highlight potential systemic weaknesses that could impact the security of countless applications relying on curl for network communication.

Several vulnerabilities revolve around the mishandling of credentials and authentication states. CVE-2026-94266 and CVE-2026-94265 detail how curl could inadvertently leak credentials in URLs or mishandle authentication states during redirects, potentially exposing sensitive information to malicious servers. CVE-2026-86414 describes how an HTTP proxy could trick libcurl into sending origin credentials to the proxy itself, rather than the intended destination. Similarly, CVE-2026-86413 and CVE-2026-86415 point to issues with credential reuse and authentication across different origins or connection types, particularly concerning Negotiate authentication and client certificate handling. CVE-2026-86416 also touches on credential leakage, where SSH host verification options might not be set correctly when following redirects. Finally, CVE-2026-86409 indicates a persistent issue with AWS SigV4 authentication state leakage.

Other vulnerabilities focus on denial-of-service and data integrity issues. CVE-2026-92391 describes a stack overflow vulnerability in libcurl's MIME handling, which could crash the host process when processing deeply nested multipart MIME structures. CVE-2026-92388 and CVE-2026-86412 highlight problems with cookie jar handling, where malformed cookies could lead to premature parsing termination or the deletion of unrelated domain cookies. CVE-2026-92387 details a bypass of transfer timeouts in FTP, IMAP, POP3, and SMTP protocols, allowing malicious servers to indefinitely block transfers. CVE-2026-86411 points to a flaw in FTP connection reuse, where a TLS-upgraded connection could be reused by a non-TLS transfer, bypassing security checks. CVE-2026-87864 describes an issue with IMAP APPEND commands where incorrect byte counts could lead to command injection. CVE-2026-87863 and CVE-2026-87862 involve HSTS (HTTP Strict Transport Security) parsing and serialization, where extreme or improperly ordered HSTS entries could lead to unencrypted HTTP requests. CVE-2026-92390 addresses a flaw in the --remote-header-name option, where anti-clobbering protections can be bypassed under certain redirect or ETag conditions. CVE-2026-92389 describes a state validation issue in the TFTP state machine, allowing malicious servers to force clients into transmit mode. CVE-2026-87865 notes an issue with libssh2's known_hosts file handling, potentially misreporting key mismatches. Lastly, CVE-2026-107929 indicates that interface binding information is not correctly used in connection reuse keys, allowing unintended connections to be reused. CVE-2026-87866, when built with wolfSSL, could lead to successful validation of a pinned public key hash against a key the peer does not possess. CVE-2026-107928 describes an out-of-bounds read in GnuTLS when processing WebSocket data.

The disclosure of these 23 vulnerabilities on October 20, 2026, underscores the critical importance of keeping curl and libcurl updated. Many of these flaws, particularly those involving credential exposure and authentication bypass, could be exploited to compromise sensitive data or gain unauthorized access to systems. The diversity of the affected protocols and functionalities means that a wide range of applications and services are potentially at risk. Users are strongly advised to consult the official curl security advisories and update to the latest patched versions as soon as possible to mitigate these risks.

The curl project has released updates to address these vulnerabilities. Specific version numbers for the patches are not detailed in the provided information, but users should refer to the official curl release notes for the most current information on affected versions and the patches applied. Given the broad impact, a prompt update is the most effective mitigation strategy.

This extensive batch of vulnerabilities serves as a stark reminder of the ongoing security challenges in widely used software components. The interconnected nature of modern software means that a vulnerability in a foundational library like libcurl can have far-reaching consequences. Continuous vigilance, regular security audits, and prompt patching are essential to maintaining a secure digital environment.

The related news coverage from The Hacker News and Cyber Security News highlights the general theme of trusted connections becoming a problem and the broad impact of such vulnerabilities across numerous installations. While these articles do not detail specific CVEs beyond those listed, they reinforce the significance of this disclosure event.

This batch of 23 vulnerabilities, all disclosed on October 20, 2026, represents a critical security event for the curl project and its users. The vulnerabilities span credential leaks, authentication bypasses, denial-of-service conditions, and protocol-specific flaws, impacting a wide array of network operations. Promptly updating curl and libcurl is essential to protect against potential exploitation.

The curl project has released updates to address these vulnerabilities. Users should consult the official curl security advisories for specific version information and patching details.

The sheer number and variety of vulnerabilities disclosed in this single batch emphasize the need for ongoing security diligence. The widespread use of curl and libcurl means these issues could affect a vast number of applications and services, making timely updates crucial.

AI-written article. Grounded in 24 CVE records listed below.