CVE-2026-92388

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

“—” 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.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-105318 (ENISA EUVD) · GHSA-r22r-3m6c-qv5r (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
72
EG 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, 2026
Patch available.
Web page

curl - FTP wildcard write callback mixup - CVE-2026-92388

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibcurl4t64 (8.18.0-1ubuntu2.8) @ resolute2026-11-12ubuntu
ubuntulibcurl4-openssl-dev (7.47.0-1ubuntu2.19+esm21) @ xenial2026-11-12ubuntu
ubuntulibcurl4t64 (8.20.0-2ubuntu11.1) @ stonking2026-11-12ubuntu
redhatcurl-main-8.23.0-0.1.hum12026-10-14redhat

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)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 8.23.0-r0: fixed in 8.23.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
curl—
  • every version up to 8.23.0-r0: fixed in 8.23.0-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
curl7.88.1-10 ... 8.9.1-2~bpo12+1 (187 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
curl8.14.1-2 ... 8.23.0~rc3-1+exp1 (88 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
curl8.14.1-2 ... 8.23.0~rc3-1+exp1 (81 versions)
  • every version on: no fix on record
—

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.

  1. 2026-11-13 05:31 UTCEchelonGraph re-scored
  2. 2026-11-13 05:31 UTCVendor advisory
  3. 2026-11-13 05:31 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  5. 2026-11-12 04:17 UTCEchelonGraph re-scored
  6. 2026-11-12 04:17 UTCVendor advisory
  7. 2026-11-12 04:17 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-11-11 02:56 UTCEchelonGraph re-scored
  10. 2026-11-11 02:56 UTCVendor advisory
  11. 2026-11-11 02:56 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-11-10 01:38 UTCEchelonGraph re-scored
  14. 2026-11-10 01:38 UTCVendor advisory
  15. 2026-11-10 01:38 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-11-09 00:25 UTCEchelonGraph re-scored
  18. 2026-11-09 00:25 UTCVendor advisory
  19. 2026-11-09 00:25 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-11-07 23:12 UTCEchelonGraph re-scored
  22. 2026-11-07 23:12 UTCVendor advisory
  23. 2026-11-07 23:12 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  25. 2026-11-06 21:57 UTCEchelonGraph re-scored
Show 53 more
  1. 2026-11-06 21:57 UTCVendor advisory
  2. 2026-11-06 21:57 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  4. 2026-11-05 20:44 UTCEchelonGraph re-scored
  5. 2026-11-05 20:44 UTCVendor advisory
  6. 2026-11-05 20:44 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  7. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  8. 2026-11-04 19:32 UTCEchelonGraph re-scored
  9. 2026-11-04 19:32 UTCVendor advisory
  10. 2026-11-04 19:32 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  11. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-11-03 18:19 UTCEchelonGraph re-scored
  13. 2026-11-03 18:19 UTCVendor advisory
  14. 2026-11-03 18:19 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-11-02 17:05 UTCEchelonGraph re-scored
  17. 2026-11-02 17:05 UTCVendor advisory
  18. 2026-11-02 17:04 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-11-01 15:51 UTCEchelonGraph re-scored
  22. 2026-11-01 15:51 UTCVendor advisory
  23. 2026-11-01 15:51 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  25. 2026-10-31 14:39 UTCEchelonGraph re-scored
  26. 2026-10-31 14:39 UTCVendor advisory
  27. 2026-10-31 14:39 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r · GitHub severity CRITICAL · GitHub CVSS 9.1
  28. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  29. 2026-10-30 13:25 UTCEchelonGraph re-scored
  30. 2026-10-30 13:25 UTCVendor advisory
  31. 2026-10-30 13:25 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r
  32. 2026-10-30 12:30 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  33. 2026-10-30 12:30 UTCEchelonGraph re-scoredFirst assessed: 9.1 CRITICAL
  34. 2026-10-30 12:30 UTCVendor advisory
  35. 2026-10-30 12:30 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r
  36. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  37. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  38. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  39. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  40. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  41. 2026-10-25 13:50 UTCEchelonGraph re-scored
  42. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  43. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  44. 2026-10-22 17:11 UTCEchelonGraph re-scored
  45. 2026-10-22 17:11 UTCVendor advisory
  46. 2026-10-22 17:11 UTCGHSA enrichmentGHSA-r22r-3m6c-qv5r
  47. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  48. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  49. 2026-10-20 21:26 UTCVendor advisory
  50. 2026-10-20 21:25 UTCNVD update
  51. 2026-10-20 20:27 UTCEchelonGraph re-scored
  52. 2026-10-20 20:27 UTCVendor advisory
  53. 2026-10-20 20:26 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92388?
CVE-2026-92388 is a critical-severity vulnerability; its CVE record was published on October 20, 2026. 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,…
When was the CVE record for CVE-2026-92388 published?
The CVE record for CVE-2026-92388 was published on October 20, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-92388 actively exploited?
CVE-2026-92388 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92388?
CVE-2026-92388 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-92388?
A fix for CVE-2026-92388 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92388 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-92388

Explore →

Is Your Infrastructure Affected by CVE-2026-92388?

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