CVE-2026-8926: When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username(without a password), like `https://user@example.com/`, curl could

criticalCVSS 9.1CVE-2026-8926

When asking curl to use a .netrc file to find credentials and at the same time specifying a URL with a username(without a password), like https://user@example.com/, curl could wrongly get and use the password for *another* user set in the .netrc file for that host if such a one exists and there is no match for the specified user.

Details

Source: NVD Recent CVEs (US · database · site)
Severity: critical — CVSS 9.1
Published: 2026-07-03
Last updated: 2026-07-07
Exploitation: Not in CISA KEV at last sync

Original advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-8926

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2026-89260.61% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 45% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-8926	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.

medium[UPDATE] [medium] cURL: Multiple vulnerabilitiescert-bund
criticalCVE-2026-8926: password leak with netrc and user in URLmsrc
unknownMultiple vulnerabilities in cURL and libcurl (June 24, 2026)cert-fr-avis

CVE-2026-8926: When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL with a username(without a password), like `https://user@example.com/`, curl could

Details

Exploitation outlook

Referenced CVEs

Same CVEs, other sources

More from NVD Recent CVEs