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.
CVE-2026-8925
CRITICALPre-NVD 9.8Trending — 6 sources updated this weekElevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0
A fix is available — apply it.
- CVSS v3
- 9.8
- EG Score
- 0.0(none)
- EPSS
- 16.0%
- KEV
- Not listed
Published
July 3, 2026
Last Modified
July 6, 2026
Advisory Details (3)
Auto-updated Jul 6, 2026No patch confirmed yet.
Vendor Advisories for CVE-2026-8925(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libcurl4t64 (8.14.1-2ubuntu1.4) @ questing | 2026-07-06 | ubuntu |
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.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× 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.
- 2026-07-06 17:36 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:30 UTCEG score recompute
- 2026-07-06 02:30 UTCVendor advisory
- 2026-07-06 02:30 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-03 08:28 UTCEG score recompute
- 2026-07-03 08:28 UTCVendor advisory
- 2026-07-03 08:26 UTCNVD updatefirst tracked
Related CVEs(same vendor)
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 6, 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 16.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 0.0.
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
Explore the affected products and dependency analysis for CVE-2026-8925
Is Your Infrastructure Affected by CVE-2026-8925?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.