When an FTP wildcard LIST operation fails, libcurl omits the restoration
path meant for successful listings, leaving the write callback set to the
internal listing parser and the write callback data pointing directly to the
easy handle. Subsequent reuse of this handle triggers an immediate crash, and
cloning it via curl_easy_duphandle() copies this corrupted state into the
duplicate. If the original handle is subsequently freed, executing a transfer
on the cloned handle causes a heap use-after-free read against the dangling
handle reference; alternatively, reusing the original or cloned handle while
changing only CURLOPT_WRITEDATA (and omitting CURLOPT_WRITEFUNCTION)
results in type confusion, forcing the internal parser to interpret incoming
server response bytes into memory at the application-supplied write data
pointer.
CVE-2026-92388
“—” beside the score: it is equal to the CVSS score beside it.
Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-20. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.1; sources differ by 0.0.
Also known asEUVD-2026-105318 (ENISA EUVD) · GHSA-r22r-3m6c-qv5r (GitHub Security Advisories)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 9.1
- EG Score
- 9.1CRITICALhigh confidence
- EG Risk
- 72EG Risk 72/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity91% × 45%Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.7%
- EPSS %ILE
- 53rd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 20, 2026
Last Modified
October 30, 2026
Advisory Details (3)
Auto-updated Oct 30, 2026curl - FTP wildcard write callback mixup - CVE-2026-92388
https://curl.se/docs/CVE-2026-92388.htmlVendor Advisories for CVE-2026-92388(3)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-92388Microsoft Security Response Center (MSRC)CriticalMicrosoft CVSS 9.1
Microsoft security update for CVE-2026-92388
- GHSA-r22r-3m6c-qv5rGitHub Security AdvisoriesCritical
When an FTP wildcard `LIST` operation fails, libcurl omits the restoration path meant for...
- RHSA-2026:82895Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
Patch Availability(4)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libcurl4t64 (8.18.0-1ubuntu2.8) @ resolute | 2026-11-12 | ubuntu |
| ubuntu | libcurl4-openssl-dev (7.47.0-1ubuntu2.19+esm21) @ xenial | 2026-11-12 | ubuntu |
| ubuntu | libcurl4t64 (8.20.0-2ubuntu11.1) @ stonking | 2026-11-12 | ubuntu |
| redhat | curl-main-8.23.0-0.1.hum1 | 2026-10-14 | 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
(5 across 5 ecosystems)
Alpine:v3.23(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| curl | — |
| — |
Alpine:v3.24(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| curl | — |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| curl | 7.88.1-10 ... 8.9.1-2~bpo12+1 (187 versions) |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| curl | 8.14.1-2 ... 8.23.0~rc3-1+exp1 (88 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| curl | 8.14.1-2 ... 8.23.0~rc3-1+exp1 (81 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(3)
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 21× in last 7d / 60× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 05:31 UTCEchelonGraph re-scored
- 2026-11-13 05:31 UTCVendor advisory
- 2026-11-13 05:31 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-12 04:17 UTCEchelonGraph re-scored
- 2026-11-12 04:17 UTCVendor advisory
- 2026-11-12 04:17 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-11 02:56 UTCEchelonGraph re-scored
- 2026-11-11 02:56 UTCVendor advisory
- 2026-11-11 02:56 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-10 01:38 UTCEchelonGraph re-scored
- 2026-11-10 01:38 UTCVendor advisory
- 2026-11-10 01:38 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-09 00:25 UTCEchelonGraph re-scored
- 2026-11-09 00:25 UTCVendor advisory
- 2026-11-09 00:25 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-07 23:12 UTCEchelonGraph re-scored
- 2026-11-07 23:12 UTCVendor advisory
- 2026-11-07 23:12 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-06 21:57 UTCEchelonGraph re-scored
Show 53 moreShow fewer
- 2026-11-06 21:57 UTCVendor advisory
- 2026-11-06 21:57 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-05 20:44 UTCEchelonGraph re-scored
- 2026-11-05 20:44 UTCVendor advisory
- 2026-11-05 20:44 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-04 19:32 UTCEchelonGraph re-scored
- 2026-11-04 19:32 UTCVendor advisory
- 2026-11-04 19:32 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-03 18:19 UTCEchelonGraph re-scored
- 2026-11-03 18:19 UTCVendor advisory
- 2026-11-03 18:19 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-02 17:05 UTCEchelonGraph re-scored
- 2026-11-02 17:05 UTCVendor advisory
- 2026-11-02 17:04 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-11-01 15:51 UTCEchelonGraph re-scored
- 2026-11-01 15:51 UTCVendor advisory
- 2026-11-01 15:51 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
- 2026-10-31 14:39 UTCEchelonGraph re-scored
- 2026-10-31 14:39 UTCVendor advisory
- 2026-10-31 14:39 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-10-30 13:25 UTCEchelonGraph re-scored
- 2026-10-30 13:25 UTCVendor advisory
- 2026-10-30 13:25 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r
- 2026-10-30 12:30 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
- 2026-10-30 12:30 UTCEchelonGraph re-scoredFirst assessed: 9.1 CRITICAL
- 2026-10-30 12:30 UTCVendor advisory
- 2026-10-30 12:30 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-25 13:50 UTCEchelonGraph re-scored
- 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-22 17:11 UTCEchelonGraph re-scored
- 2026-10-22 17:11 UTCVendor advisory
- 2026-10-22 17:11 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-20 21:26 UTCVendor advisory
- 2026-10-20 21:25 UTCNVD update
- 2026-10-20 20:27 UTCEchelonGraph re-scored
- 2026-10-20 20:27 UTCVendor advisory
- 2026-10-20 20:26 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownDebian:12:curl
- CVE-2026-19931EG 9.8CRITICAL
- CVE-2026-11856EG 9.8CRITICAL
- CVE-2026-10536EG 9.8CRITICAL
- CVE-2023-38545NVD 8.8EG 9.8EPSS p100CRITICAL
- CVE-2023-27536NVD 5.9EG 9.8CRITICAL
- CVE-2022-32221EG 9.8EPSS p92CRITICAL
- CVE-2022-42915NVD 8.1EG 9.8EPSS p90CRITICAL
- CVE-2022-32207EG 9.8EPSS p96CRITICAL
- CVE-2019-5482EG 9.8EPSS p97CRITICAL
- CVE-2019-5481EG 9.8EPSS p95CRITICAL
Same vendor
10 shownredhat:RHSA-2026:82895
Frequently asked(5)
What is CVE-2026-92388?
When was the CVE record for CVE-2026-92388 published?
Is CVE-2026-92388 actively exploited?
What is the CVSS score of CVE-2026-92388?
How do I remediate CVE-2026-92388?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-92388
Is Your Infrastructure Affected by CVE-2026-92388?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.