When doing a second SMB request to the same host again, curl would wrongly use a data pointer pointing into already freed memory.
CVE-2026-3805
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-03-11. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 1%
- EPSS %ILE
- 53%
- KEV
- Not listed
Published
March 11, 2026
Last Modified
September 15, 2026
Advisory Details (4)
Auto-updated Aug 2, 2026oss-security - [ADVISORY] curl: CVE-2026-3805: use after free in SMB connection reuse
http://www.openwall.com/lists/oss-security/2026/03/11/4curl - use after free in SMB connection reuse - CVE-2026-3805
https://curl.se/docs/CVE-2026-3805.htmlVendor Advisories for CVE-2026-3805(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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libcurl4t64 (8.14.1-2ubuntu1.2) @ questing | 2026-09-15 | ubuntu |
| redhat | curl-main-8.19.0-3.hum1 | 2026-04-07 | redhat |
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
(4 across 4 ecosystems)
Alpine:v3.23(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.19.0-r0 | — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | — | 8.19.0-r0 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | 8.14.1-2, 8.14.1-2+deb13u1, 8.14.1-2+deb13u2, 8.14.1-2+deb13u2~bpo13+1, 8.14.1-2+deb13u3 | 8.14.1-2+deb13u4 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| curl | 8.14.1-2 ... 8.19.0~rc3-1 (36 versions) | 8.19.0-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 15× in last 7d / 36× 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 104 total refreshes for this CVE.
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 19:30 UTCEPSS rescore
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 06:40 UTCEG score recompute
- 2026-09-15 06:40 UTCVendor advisory
- 2026-09-15 06:40 UTCGHSA enrichment
- 2026-09-15 03:11 UTCEPSS rescore
- 2026-09-14 21:34 UTCVendor advisory
- 2026-09-14 21:34 UTCGHSA enrichment
- 2026-09-14 20:45 UTCEG score recompute
- 2026-09-14 20:45 UTCVendor advisory
- 2026-09-14 20:45 UTCGHSA enrichment
- 2026-09-13 16:47 UTCEPSS rescore
- 2026-09-12 15:01 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 09:37 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-08 22:00 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 20:10 UTCOSV refresh
- 2026-09-02 14:12 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:55 UTCEG score recompute
- 2026-08-16 11:55 UTCVendor advisory
- 2026-08-16 11:55 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 20:13 UTCVendor advisory
- 2026-08-14 20:13 UTCGHSA enrichment
- 2026-08-14 07:52 UTCEG score recompute
- 2026-08-14 07:52 UTCVendor advisory
- 2026-08-14 07:52 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 23:05 UTCEG score recompute
- 2026-08-12 23:05 UTCVendor advisory
- 2026-08-12 23:05 UTCGHSA enrichment
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 21:52 UTCEG score recompute
- 2026-08-11 21:52 UTCVendor advisory
- 2026-08-11 21:52 UTCGHSA enrichment
- 2026-08-11 13:43 UTCEPSS rescore
- 2026-08-11 05:00 UTCEG score recompute
- 2026-08-11 05:00 UTCVendor advisory
- 2026-08-11 05:00 UTCGHSA enrichment
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 06:46 UTCVendor advisory
- 2026-08-10 06:46 UTCGHSA enrichment
- 2026-08-09 18:53 UTCEG score recompute
- 2026-08-09 18:53 UTCVendor advisory
- 2026-08-09 18:53 UTCGHSA enrichment
- 2026-08-09 13:46 UTCEPSS rescore
- 2026-08-09 07:33 UTCEG score recompute
- 2026-08-09 07:33 UTCVendor advisory
- 2026-08-09 07:33 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-08 05:42 UTCVendor advisory
- 2026-08-08 05:42 UTCGHSA enrichment
- 2026-08-07 18:22 UTCEG score recompute
- 2026-08-07 18:22 UTCVendor advisory
- 2026-08-07 18:22 UTCGHSA enrichment
- 2026-08-06 19:56 UTCEG score recompute
- 2026-08-06 19:56 UTCVendor advisory
- 2026-08-06 19:56 UTCGHSA enrichment
- 2026-08-06 13:46 UTCEPSS rescore
- 2026-08-06 02:04 UTCEG score recompute
- 2026-08-06 02:04 UTCVendor advisory
- 2026-08-06 02:04 UTCGHSA enrichment
- 2026-08-05 19:17 UTCEPSS rescore
- 2026-08-04 15:10 UTCEPSS rescore
- 2026-08-04 10:38 UTCEPSS rescore
- 2026-08-04 01:23 UTCEG score recompute
- 2026-08-04 01:23 UTCVendor advisory
- 2026-08-04 01:23 UTCGHSA enrichment
- 2026-08-03 10:36 UTCEPSS rescore
- 2026-08-02 17:39 UTCEG score recompute
- 2026-08-02 17:39 UTCVendor advisory
- 2026-08-02 17:39 UTCGHSA enrichment
- 2026-08-02 02:27 UTCEPSS rescore
- 2026-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:28 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-27 14:13 UTCEPSS rescore
Frequently asked(5)
What is CVE-2026-3805?
When was CVE-2026-3805 disclosed?
Is CVE-2026-3805 actively exploited?
What is the CVSS score of CVE-2026-3805?
How do I remediate CVE-2026-3805?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3805
Is Your Infrastructure Affected by CVE-2026-3805?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.