CVE-2026-9079

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-03. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

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

A fix is available — apply it.

libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (3)

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

curl - stale proxy password leak - CVE-2026-9079

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4t64 (8.18.0-1ubuntu2.2) @ resolute2026-08-21ubuntu
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

(3 across 3 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
curl8.21.0-r0
Debian:13(1)
PackageVulnerable rangeFixed inDependents
curl8.14.1-2 ... 8.21.0~rc3-1+exp1 (74 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 81× in last 7d / 327× 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 441 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-9079?
CVE-2026-9079 is a critical vulnerability published on July 3, 2026. libcurl had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.
When was CVE-2026-9079 disclosed?
CVE-2026-9079 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-9079 actively exploited?
CVE-2026-9079 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.6% of all scored CVEs.
What is the CVSS score of CVE-2026-9079?
CVE-2026-9079 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-9079?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9079, 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-9079

Explore →

Is Your Infrastructure Affected by CVE-2026-9079?

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