Description
A flaw was found in curl. In builds configured with the Microsoft Schannel Transport Layer Security (TLS) backend, libcurl's connection cache fails to evaluate client certificate authentication settings when handling HTTP redirects. A malicious server can redirect a transfer to a different destination, causing curl to inappropriately reuse an already authenticated connection. This issue can result in information disclosure by exposing client certificates and credentials to unintended origins.
Published: n/a
Score: 3.7 Low
EPSS: n/a
KEV: No
Impact: Information Disclosure
Action: Update
AI Analysis

Impact

The flaw lies in libcurl's connection cache when using the Microsoft Schannel TLS backend. The connection cache fails to reassess client certificate authentication during HTTP redirects, allowing a malicious server to redirect a transfer to a different destination. In doing so, libcurl reuses an already authenticated connection and can expose the client’s certificate and credentials to an unintended origin, potentially leaking sensitive authentication data.

Affected Systems

This issue affects any curl (libcurl) build compiled with the Microsoft Schannel TLS backend. No specific version range is provided, so all such builds may be susceptible.

Risk and Exploitability

The CVSS score of 3.7 indicates low severity, and the EPSS score is not available, suggesting limited evidence of exploitation. The vulnerability is not listed in the CISA KEV catalog. Nonetheless, an attacker able to control a redirecting server can exploit the flaw to gain client certificates, which could aid in credential compromise or lateral movement. The overall risk is low to moderate, warranting attention but not immediate emergency response.

Generated by OpenCVE AI on October 17, 2026 at 01:50 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade libcurl to the latest version that incorporates the fix for the Schannel backend connection cache issue.
  • Disable or carefully regulate automatic HTTP redirects in client applications that handle sensitive credentials to prevent unintended connection reuse.
  • Configure curl to use an alternative TLS backend instead of Microsoft Schannel when possible to avoid the vulnerable code path.

Generated by OpenCVE AI on October 17, 2026 at 01:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 18 Oct 2026 14:30:00 +0000

Type Values Removed Values Added
First Time appeared Curl
Curl curl
Vendors & Products Curl
Curl curl

Sat, 17 Oct 2026 00:30:00 +0000

Type Values Removed Values Added
Description A flaw was found in curl. In builds configured with the Microsoft Schannel Transport Layer Security (TLS) backend, libcurl's connection cache fails to evaluate client certificate authentication settings when handling HTTP redirects. A malicious server can redirect a transfer to a different destination, causing curl to inappropriately reuse an already authenticated connection. This issue can result in information disclosure by exposing client certificates and credentials to unintended origins.
Title curl: curl: auto client cert connection reuse mixup
Weaknesses CWE-201
References
Metrics threat_severity

None

cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N'}

threat_severity

Low


cve-icon MITRE

No data.

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity : Low

Publid Date: 2026-10-14T12:00:00Z

Links: CVE-2026-86415 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-18T14:15:14Z

Weaknesses
  • CWE-201

    Insertion of Sensitive Information Into Sent Data