CVE-2026-8926

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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://[email protected]/, 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 v3
9.1
EG Score
9.1(medium)
EG Risk
57(Track*)
EG Risk 57/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Sep 8, 2026
No patch confirmed yet.
generic

HackerOne

https://hackerone.com/reports/3735184
generic
https://curl.se/docs/CVE-2026-8926.json
generic

curl - password leak with netrc and user in URL - CVE-2026-8926

https://curl.se/docs/CVE-2026-8926.html

Vendor 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.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4t64 (8.18.0-1ubuntu2.2) @ resolute2026-09-06ubuntu
redhatrust-main-1.96.1-1.hum12026-07-02redhat
redhatcurl-main-8.21.0-0.1.hum12026-06-24redhat

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.

Affected Packages

(4 across 4 ecosystems)
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
curl—8.22.0-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
curl—8.21.0-r0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.22.0~rc3-1+exp1 (78 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.21.0~rc1-1+exp1 (59 versions)8.21.0~rc2-1—

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 14× in last 7d / 195× 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 544 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:38 UTCEPSS rescore
  3. 2026-09-10 09:35 UTCEPSS rescore
  4. 2026-09-08 22:01 UTCEPSS rescore
  5. 2026-09-06 14:18 UTCEG score recompute
  6. 2026-09-06 14:18 UTCVendor advisory
  7. 2026-09-06 14:18 UTCGHSA enrichment
  8. 2026-09-06 13:48 UTCEPSS rescore
  9. 2026-09-06 04:52 UTCVendor advisory
  10. 2026-09-06 04:52 UTCGHSA enrichment
  11. 2026-09-05 23:48 UTCEG score recompute
  12. 2026-09-05 23:48 UTCVendor advisory
  13. 2026-09-05 23:48 UTCGHSA enrichment
  14. 2026-09-05 15:31 UTCEPSS rescore
  15. 2026-09-04 05:07 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-01 13:54 UTCEPSS rescore
  18. 2026-09-01 04:40 UTCEPSS rescore
  19. 2026-08-31 01:30 UTCVendor advisory
  20. 2026-08-31 01:30 UTCGHSA enrichment
  21. 2026-08-30 21:10 UTCEG score recompute
  22. 2026-08-30 21:10 UTCVendor advisory
  23. 2026-08-30 21:10 UTCGHSA enrichment
  24. 2026-08-30 19:18 UTCEPSS rescore
  25. 2026-08-30 16:50 UTCVendor advisory
Show 75 more
  1. 2026-08-30 16:50 UTCGHSA enrichment
  2. 2026-08-30 11:20 UTCEG score recompute
  3. 2026-08-30 11:20 UTCVendor advisory
  4. 2026-08-30 11:20 UTCGHSA enrichment
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:42 UTCEPSS rescore
  7. 2026-08-28 02:45 UTCVendor advisory
  8. 2026-08-28 02:45 UTCGHSA enrichment
  9. 2026-08-27 22:12 UTCEG score recompute
  10. 2026-08-27 22:12 UTCVendor advisory
  11. 2026-08-27 22:12 UTCGHSA enrichment
  12. 2026-08-27 14:25 UTCEPSS rescore
  13. 2026-08-27 03:15 UTCEG score recompute
  14. 2026-08-27 03:15 UTCVendor advisory
  15. 2026-08-27 03:15 UTCGHSA enrichment
  16. 2026-08-26 14:47 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-25 13:38 UTCVendor advisory
  19. 2026-08-25 13:38 UTCGHSA enrichment
  20. 2026-08-25 05:34 UTCVendor advisory
  21. 2026-08-25 05:34 UTCGHSA enrichment
  22. 2026-08-25 01:14 UTCVendor advisory
  23. 2026-08-25 01:14 UTCGHSA enrichment
  24. 2026-08-24 20:55 UTCVendor advisory
  25. 2026-08-24 20:54 UTCGHSA enrichment
  26. 2026-08-24 15:15 UTCEG score recompute
  27. 2026-08-24 15:15 UTCVendor advisory
  28. 2026-08-24 15:15 UTCGHSA enrichment
  29. 2026-08-24 14:18 UTCEPSS rescore
  30. 2026-08-24 10:54 UTCEG score recompute
  31. 2026-08-24 10:54 UTCVendor advisory
  32. 2026-08-24 10:54 UTCGHSA enrichment
  33. 2026-08-24 06:33 UTCVendor advisory
  34. 2026-08-24 06:33 UTCGHSA enrichment
  35. 2026-08-24 01:43 UTCVendor advisory
  36. 2026-08-24 01:43 UTCGHSA enrichment
  37. 2026-08-23 21:22 UTCVendor advisory
  38. 2026-08-23 21:22 UTCGHSA enrichment
  39. 2026-08-23 16:59 UTCVendor advisory
  40. 2026-08-23 16:59 UTCGHSA enrichment
  41. 2026-08-23 12:39 UTCVendor advisory
  42. 2026-08-23 12:39 UTCGHSA enrichment
  43. 2026-08-23 08:19 UTCVendor advisory
  44. 2026-08-23 08:19 UTCGHSA enrichment
  45. 2026-08-23 03:59 UTCEG score recompute
  46. 2026-08-23 03:59 UTCVendor advisory
  47. 2026-08-23 03:59 UTCGHSA enrichment
  48. 2026-08-23 00:19 UTCEPSS rescore
  49. 2026-08-22 23:38 UTCVendor advisory
  50. 2026-08-22 23:38 UTCGHSA enrichment
  51. 2026-08-22 19:18 UTCVendor advisory
  52. 2026-08-22 19:18 UTCGHSA enrichment
  53. 2026-08-22 14:46 UTCVendor advisory
  54. 2026-08-22 14:46 UTCGHSA enrichment
  55. 2026-08-22 10:23 UTCVendor advisory
  56. 2026-08-22 10:23 UTCGHSA enrichment
  57. 2026-08-22 05:59 UTCEG score recompute
  58. 2026-08-22 05:59 UTCVendor advisory
  59. 2026-08-22 05:59 UTCGHSA enrichment
  60. 2026-08-21 23:49 UTCEPSS rescore
  61. 2026-08-21 23:30 UTCVendor advisory
  62. 2026-08-21 23:30 UTCGHSA enrichment
  63. 2026-08-21 19:05 UTCVendor advisory
  64. 2026-08-21 19:05 UTCGHSA enrichment
  65. 2026-08-21 14:39 UTCVendor advisory
  66. 2026-08-21 14:39 UTCGHSA enrichment
  67. 2026-08-21 10:19 UTCVendor advisory
  68. 2026-08-21 10:19 UTCGHSA enrichment
  69. 2026-08-21 05:59 UTCVendor advisory
  70. 2026-08-21 05:59 UTCGHSA enrichment
  71. 2026-08-21 01:38 UTCEG score recompute
  72. 2026-08-21 01:38 UTCVendor advisory
  73. 2026-08-21 01:38 UTCGHSA enrichment
  74. 2026-08-20 22:56 UTCEPSS rescore
  75. 2026-08-20 21:18 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-8926?
CVE-2026-8926 is a critical vulnerability published on July 3, 2026. 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://[email protected]/, 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…
When was CVE-2026-8926 disclosed?
CVE-2026-8926 was first published in the National Vulnerability Database on July 3, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8926 actively exploited?
CVE-2026-8926 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 62.6% of all scored CVEs.
What is the CVSS score of CVE-2026-8926?
CVE-2026-8926 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-8926?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8926, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-8926

Explore →

Is Your Infrastructure Affected by CVE-2026-8926?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs