CVE-2026-8927

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH 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 reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against proxyA using Digest auth, a subsequent transfer routed through proxyB erroneously leaks the Proxy-Authorization: header intended solely for proxyA.

CVSS v3
9.1
EG Score
9.1(high)
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
36%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Jul 6, 2026
No patch confirmed yet.
generic

curl - env-set cross-proxy Digest auth state leak - CVE-2026-8927

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4-openssl-dev (7.81.0-1ubuntu1.25) @ jammy2026-07-27ubuntu
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.

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 28× in last 7d / 162× 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 162 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-8927?
CVE-2026-8927 is a critical vulnerability published on July 3, 2026. When reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against proxyA using Digest auth, a subsequent transfer routed…
When was CVE-2026-8927 disclosed?
CVE-2026-8927 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-8927 actively exploited?
CVE-2026-8927 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 64.0% of all scored CVEs.
What is the CVSS score of CVE-2026-8927?
CVE-2026-8927 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-8927?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8927, 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-8927

Explore →

Is Your Infrastructure Affected by CVE-2026-8927?

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