CVE-2026-8925

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.

The curl logic that works with SASL authentication could end up cleaning up the GSASL context *twice* without clearing the pointer in between, making it free() the same pointer twice.

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
46%
KEV
Not listed

Published

July 3, 2026

Last Modified

July 7, 2026

Advisory Details (3)

Auto-updated Aug 16, 2026
No patch confirmed yet.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibcurl4t64 (8.5.0-2ubuntu10.10) @ noble2026-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

(2 across 2 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
curl8.21.0-r0
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 86× in last 7d / 355× 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 485 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-8925?
CVE-2026-8925 is a critical vulnerability published on July 3, 2026. The curl logic that works with SASL authentication could end up cleaning up the GSASL context twice without clearing the pointer in between, making it free() the same pointer twice.
When was CVE-2026-8925 disclosed?
CVE-2026-8925 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-8925 actively exploited?
CVE-2026-8925 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-8925?
CVE-2026-8925 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-8925?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8925, 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-8925

Explore →

Is Your Infrastructure Affected by CVE-2026-8925?

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