CVE-2026-6429

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-05-14. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 5.3Exploit: NoneExposed: 0

A fix is available — apply it.

When asked to both use a .netrc file for credentials and to follow HTTP redirects, libcurl could leak the password used for the first host to the followed-to host under certain circumstances.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
41.0%
KEV
Not listed

Published

May 13, 2026

Last Modified

May 14, 2026

Advisory Details (3)

Auto-updated Jun 17, 2026
No patch confirmed yet.
generic

curl - netrc credential leak with reused proxy connection - CVE-2026-6429

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

Vendor Advisories for CVE-2026-6429(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4t64 (8.5.0-2ubuntu10.9) @ noble2026-06-27ubuntu
redhatcurl-main-8.20.0-0.1.hum12026-05-02redhat

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.

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 11× in last 7d / 52× 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 134 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6429?
CVE-2026-6429 is a medium vulnerability published on May 13, 2026. When asked to both use a .netrc file for credentials and to follow HTTP redirects, libcurl could leak the password used for the first host to the followed-to host under certain circumstances.
When was CVE-2026-6429 disclosed?
CVE-2026-6429 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on May 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6429 actively exploited?
CVE-2026-6429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 41.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6429?
CVE-2026-6429 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-6429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6429, 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

Explore the affected products and dependency analysis for CVE-2026-6429

Explore →

Is Your Infrastructure Affected by CVE-2026-6429?

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