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 wrongly get and use the password for *another* user set in the `.netrc`…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.44%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.1
- 9.1 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- EPSS
- 0.44% probability · 38th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-522
- Affected
- haxx/curl
- Source
- 2499f714-1537-4658-8207-48ae4bb9eae9
References
- https://curl.se/docs/CVE-2026-8926.htmlPatch, Vendor Advisory
- https://curl.se/docs/CVE-2026-8926.jsonVendor Advisory
- https://hackerone.com/reports/3735184Exploit, Issue Tracking, Third Party Advisory
- https://hackerone.com/reports/3735184Exploit, Issue Tracking, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.