Description
A flaw was found in curl. A malicious or compromised HTTP proxy server can trick curl into sending authentication credentials intended for the target destination server directly to the proxy itself. When establishing a connection tunnel, if the proxy replies with an HTTP 401 Unauthorized status code instead of a proxy authentication challenge, curl mishandles the response and transmits the origin server's credentials. This issue leads to information disclosure, allowing an untrusted proxy to intercept sensitive passwords and authentication tokens.
Published: n/a
Score: 6.5 Medium
EPSS: n/a
KEV: No
Impact: Information Disclosure
Action: Patch Update
AI Analysis

Impact

The flaw in curl causes the program to inadvertently forward authentication credentials intended for the target server to an HTTP proxy. When the proxy returns an HTTP 401 Unauthorized status instead of a proper 407 Proxy Authentication Required challenge during a tunnel setup, curl misinterprets the response and transmits the origin server’s credentials. The result is that an attacker controlling or compromising a proxy can obtain sensitive passwords and authentication tokens. This vulnerability specifically reflects a credential disclosure weakness, as catalogued by CWE-201.

Affected Systems

All systems that use the curl utility and rely on proxy routing are potentially impacted, regardless of operating system. The exact affected versions are not specified in the public advisory, so any installation of curl that has not been updated to a release containing the fix could be vulnerable.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity, and no EPSS score is available to gauge current exploitation likelihood. The vulnerability is not listed in CISA’s KEV catalog, suggesting no known widespread exploitation as of the latest data. An attacker would need to control or compromise a proxy that the client is configured to use; the attack is feasible if a proxy server misbehaves or is malicious. Once the proxy is capable of sending an HTTP 401 response, credentials for the destination host can be captured, leading to information disclosure. The primary vector is an untrusted or compromised HTTP proxy used by curl client instances.

Generated by OpenCVE AI on October 18, 2026 at 21:16 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade curl to the latest released version that contains the fix for the credential leakage issue.
  • If an upgrade is not immediately available, configure curl to bypass the proxy for the target host using the --noproxy option or by explicitly specifying trusted proxy settings such that the proxy is required to present a proper 407 authentication challenge before tunneling.
  • Monitor client logs for unexpected 401 Unauthorized responses from proxies, as these indicate the potential misuse of credentials and can trigger a review of proxy configuration and trust boundaries.

Generated by OpenCVE AI on October 18, 2026 at 21:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Ubuntu USN Ubuntu USN USN-8927-1 curl vulnerabilities
Ubuntu USN Ubuntu USN USN-8932-1 curl vulnerabilities
History

Sun, 18 Oct 2026 20:15:00 +0000

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

Thu, 15 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
Description A flaw was found in curl. A malicious or compromised HTTP proxy server can trick curl into sending authentication credentials intended for the target destination server directly to the proxy itself. When establishing a connection tunnel, if the proxy replies with an HTTP 401 Unauthorized status code instead of a proxy authentication challenge, curl mishandles the response and transmits the origin server's credentials. This issue leads to information disclosure, allowing an untrusted proxy to intercept sensitive passwords and authentication tokens.
Title curl: curl: leaking host credentials to HTTP proxy
Weaknesses CWE-201
References
Metrics threat_severity

None

cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/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-86414 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-18T21:30:14Z

Weaknesses
  • CWE-201

    Insertion of Sensitive Information Into Sent Data