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.
CVE-2026-8926
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1(high)
- EG Risk
- —
- EPSS
- 45.5%
- KEV
- Not listed
Published
July 3, 2026
Last Modified
July 7, 2026
Advisory Details (3)
Auto-updated Jul 6, 2026curl - password leak with netrc and user in URL - CVE-2026-8926
https://curl.se/docs/CVE-2026-8926.htmlVendor Advisories for CVE-2026-8926(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-8926Microsoft Security Response Center (MSRC)Medium
password leak with netrc and user in URL
- GHSA-vw2x-3w8j-rq82GitHub Security AdvisoriesCritical
When asking curl to use a `.netrc` file to find credentials and at the same time specifying a URL...
- RHSA-2026:34975Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- RHSA-2026:29017Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libcurl4-openssl-dev (7.81.0-1ubuntu1.25) @ jammy | 2026-07-16 | ubuntu |
| redhat | rust-main-1.96.1-1.hum1 | 2026-07-02 | redhat |
| redhat | curl-main-8.21.0-0.1.hum1 | 2026-06-24 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(1)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 22× in last 7d / 119× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 119 total refreshes for this CVE.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-21 15:25 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-17 02:45 UTCVendor advisory
- 2026-07-17 02:45 UTCGHSA enrichment
- 2026-07-16 22:25 UTCVendor advisory
- 2026-07-16 22:25 UTCGHSA enrichment
- 2026-07-16 18:04 UTCVendor advisory
- 2026-07-16 18:04 UTCGHSA enrichment
- 2026-07-16 17:03 UTCEPSS rescore
- 2026-07-16 13:44 UTCVendor advisory
- 2026-07-16 13:44 UTCGHSA enrichment
- 2026-07-16 09:23 UTCVendor advisory
- 2026-07-16 09:23 UTCGHSA enrichment
- 2026-07-16 05:02 UTCVendor advisory
- 2026-07-16 05:02 UTCGHSA enrichment
- 2026-07-16 00:41 UTCVendor advisory
- 2026-07-16 00:41 UTCGHSA enrichment
- 2026-07-15 20:21 UTCVendor advisory
- 2026-07-15 20:21 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-15 16:01 UTCVendor advisory
- 2026-07-15 16:01 UTCGHSA enrichment
- 2026-07-15 11:41 UTCVendor advisory
- 2026-07-15 11:41 UTCGHSA enrichment
- 2026-07-15 07:17 UTCVendor advisory
- 2026-07-15 07:17 UTCGHSA enrichment
- 2026-07-15 02:55 UTCVendor advisory
- 2026-07-15 02:55 UTCGHSA enrichment
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-14 22:35 UTCVendor advisory
- 2026-07-14 22:35 UTCGHSA enrichment
- 2026-07-14 18:15 UTCVendor advisory
- 2026-07-14 18:15 UTCGHSA enrichment
- 2026-07-14 13:55 UTCVendor advisory
- 2026-07-14 13:55 UTCGHSA enrichment
- 2026-07-14 09:35 UTCVendor advisory
- 2026-07-14 09:35 UTCGHSA enrichment
- 2026-07-14 05:14 UTCVendor advisory
- 2026-07-14 05:14 UTCGHSA enrichment
- 2026-07-14 00:53 UTCVendor advisory
- 2026-07-14 00:53 UTCGHSA enrichment
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 20:33 UTCVendor advisory
- 2026-07-13 20:32 UTCGHSA enrichment
- 2026-07-13 16:12 UTCVendor advisory
- 2026-07-13 16:12 UTCGHSA enrichment
- 2026-07-13 11:46 UTCVendor advisory
- 2026-07-13 11:46 UTCGHSA enrichment
- 2026-07-13 07:24 UTCVendor advisory
- 2026-07-13 07:24 UTCGHSA enrichment
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 03:04 UTCVendor advisory
- 2026-07-13 03:03 UTCGHSA enrichment
- 2026-07-12 22:42 UTCVendor advisory
- 2026-07-12 22:42 UTCGHSA enrichment
- 2026-07-12 18:22 UTCVendor advisory
- 2026-07-12 18:22 UTCGHSA enrichment
- 2026-07-12 13:59 UTCVendor advisory
- 2026-07-12 13:58 UTCGHSA enrichment
- 2026-07-12 09:38 UTCVendor advisory
- 2026-07-12 09:38 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 05:18 UTCVendor advisory
- 2026-07-12 05:18 UTCGHSA enrichment
- 2026-07-12 00:58 UTCVendor advisory
- 2026-07-12 00:58 UTCGHSA enrichment
- 2026-07-11 20:38 UTCVendor advisory
- 2026-07-11 20:38 UTCGHSA enrichment
- 2026-07-11 16:18 UTCVendor advisory
- 2026-07-11 16:18 UTCGHSA enrichment
- 2026-07-11 11:58 UTCVendor advisory
- 2026-07-11 11:58 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 07:37 UTCVendor advisory
- 2026-07-11 07:37 UTCGHSA enrichment
- 2026-07-11 03:17 UTCVendor advisory
- 2026-07-11 03:17 UTCGHSA enrichment
- 2026-07-10 22:57 UTCVendor advisory
- 2026-07-10 22:57 UTCGHSA enrichment
- 2026-07-10 18:37 UTCVendor advisory
- 2026-07-10 18:36 UTCGHSA enrichment
- 2026-07-10 14:16 UTCVendor advisory
- 2026-07-10 14:16 UTCGHSA enrichment
- 2026-07-10 09:56 UTCVendor advisory
- 2026-07-10 09:55 UTCGHSA enrichment
- 2026-07-10 05:35 UTCVendor advisory
- 2026-07-10 05:35 UTCGHSA enrichment
- 2026-07-10 01:13 UTCVendor advisory
- 2026-07-10 01:13 UTCGHSA enrichment
- 2026-07-09 20:53 UTCVendor advisory
- 2026-07-09 20:53 UTCGHSA enrichment
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 16:33 UTCVendor advisory
- 2026-07-09 16:33 UTCGHSA enrichment
- 2026-07-09 12:08 UTCVendor advisory
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat · msrc
- CVE-2001-0414NVD 0.0EG 9.0EPSS 100%NONE
- CVE-1999-0236EG 7.5EPSS 98%HIGH
- CVE-2001-0550NVD 0.0EG 7.3EPSS 99%NONE
- CVE-1999-0612NVD 0.0EG 6.1EPSS 99%NONE
- CVE-2001-0731NVD 0.0EG 4.4EPSS 99%NONE
- CVE-1999-0524EG 4.1EPSS 98%MEDIUM
- CVE-2001-0554NVD 0.0EG 1.3EPSS 98%NONE
- CVE-1999-1412NVD 0.0EG 0.9EPSS 98%NONE
- CVE-2001-0010NVD 0.0EG 0.3EPSS 98%NONE
- CVE-2001-0887EG 0.0NONE
Same CWE
10 shownCWE-522
- CVE-2013-7055EG 9.8EPSS 93%CRITICAL
- CVE-2013-7052EG 9.8EPSS 98%CRITICAL
- CVE-2014-3445EG 9.8EPSS 92%CRITICAL
- CVE-2014-5381EG 9.8EPSS 94%CRITICAL
- CVE-2014-5093EG 9.8CRITICAL
- CVE-2016-4401EG 9.8CRITICAL
- CVE-2018-1000627EG 9.8CRITICAL
- CVE-2018-11742EG 9.8EPSS 96%CRITICAL
- CVE-2018-1000851EG 9.8CRITICAL
- CVE-2018-10824EG 9.8EPSS 96%CRITICAL
Frequently asked(5)
What is CVE-2026-8926?
When was CVE-2026-8926 disclosed?
Is CVE-2026-8926 actively exploited?
What is the CVSS score of CVE-2026-8926?
How do I remediate CVE-2026-8926?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-8926
Is Your Infrastructure Affected by CVE-2026-8926?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.