CVE-2024-51745

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 0.8% (58th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-3231 (ENISA EUVD) · GHSA-c2f5-jxjv-2hh8 (GitHub Security Advisories) · RUSTSEC-2024-0438 (OSV.dev)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 10.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Wasmtime is a fast and secure runtime for WebAssembly. Wasmtime's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however it did not block access to the special device filenames which use superscript digits, such as "COM¹", "COM²", "LPT⁰", "LPT¹", and so on. Untrusted Wasm programs that are given access to any filesystem directory could bypass the sandbox and access devices through those special device filenames with superscript digits, and through them gain access peripheral devices connected to the computer, or network resources mapped to those devices. This can include modems, printers, network printers, and any other device connected to a serial or parallel port, including emulated USB serial ports. Patch releases for Wasmtime have been issued as 24.0.2, 25.0.3, and 26.0.1. Users of Wasmtime 23.0.x and prior are recommended to upgrade to one of these patched versions. There are no known workarounds for this issue. Affected Windows users are recommended to upgrade.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
45
EG Risk 45/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.8%
EPSS %ILE
58th
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.8% 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

November 5, 2024

Last Modified

September 4, 2025

Advisory Details (4)

Auto-updated Nov 8, 2026
Patch available. Sources: github, github_pr.
Web page

Naming Files, Paths, and Namespaces - Win32 apps | Microsoft Learn

https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions
GitHub advisoryMentions a patch (unverified)

Wasmtime doesn't fully sandbox all the Windows device filenames · Advisory · bytecodealliance/wasmtime · GitHub

https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-c2f5-jxjv-2hh8
GitHub pull request

Add missing reserved file names

Fix merged in bytecodealliance/cap-std PR #371 on 2024-11-05 — awaiting tagged release

https://github.com/bytecodealliance/cap-std/pull/371
Web page

ISO/IEC 8859-1 - Wikipedia

https://en.wikipedia.org/wiki/ISO/IEC_8859-1

Vendor Advisories for CVE-2024-51745(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rustwasmtime @ 24.0.2 (fixes < 24.0.2)—ghsa
rustwasmtime @ 26.0.1 (fixes = 26.0.0)—ghsa
rustwasmtime @ 25.0.3 (fixes >= 25.0.0, < 25.0.3)—ghsa

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

(3 across 3 ecosystems)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
wasmtime26.0.0
  • every version up to 24.0.2: fixed in 24.0.2
  • 25.0.0 up to 25.0.3: fixed in 25.0.3
  • 26.0.0 up to 26.0.1: fixed in 26.0.1
  • 0.0.0-0 up to 24.0.2: fixed in 24.0.2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rust-wasmtime—
  • every version up to 26.0.1+dfsg-1: fixed in 26.0.1+dfsg-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rust-wasmtime—
  • every version up to 26.0.1+dfsg-1: fixed in 26.0.1+dfsg-1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 45× 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.

Showing the most recent 100 of 271 rows on record for this CVE, as 99 entries (1 repeat merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 171 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 00:26 UTCEchelonGraph re-scored
  2. 2026-11-13 00:26 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  3. 2026-11-12 16:31 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  4. 2026-11-12 02:49 UTCEchelonGraph re-scored
  5. 2026-11-12 02:49 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  6. 2026-11-11 16:35 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  7. 2026-11-11 05:11 UTCEchelonGraph re-scored
  8. 2026-11-11 05:11 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  9. 2026-11-10 16:39 UTCEPSS rescoreEPSS 0.8% · 58th percentile
  10. 2026-11-10 07:33 UTCEchelonGraph re-scored
  11. 2026-11-10 07:33 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  12. 2026-11-09 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  13. 2026-11-09 09:55 UTCEchelonGraph re-scored
  14. 2026-11-09 09:55 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  15. 2026-11-08 16:36 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  16. 2026-11-08 12:18 UTCEchelonGraph re-scored
  17. 2026-11-08 12:18 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  18. 2026-11-07 16:36 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  19. 2026-11-07 14:38 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  20. 2026-11-06 17:00 UTCEchelonGraph re-scored
  21. 2026-11-06 17:00 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  22. 2026-11-06 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  23. 2026-11-05 19:22 UTCEchelonGraph re-scored
  24. 2026-11-05 19:22 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  25. 2026-11-05 16:34 UTCEPSS rescoreEPSS 0.8% · 57th percentile
Show 74 more
  1. 2026-11-05 04:25 UTCOSV refresh
  2. 2026-11-04 21:44 UTCEchelonGraph re-scored
  3. 2026-11-04 21:44 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  4. 2026-11-04 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  5. 2026-11-04 00:05 UTCEchelonGraph re-scored
  6. 2026-11-04 00:05 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  7. 2026-11-03 16:43 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  8. 2026-11-03 02:27 UTCEchelonGraph re-scored
  9. 2026-11-03 02:27 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  10. 2026-11-02 16:41 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  11. 2026-11-02 04:49 UTCEchelonGraph re-scored
  12. 2026-11-02 04:49 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  13. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  14. 2026-11-01 08:11 UTCGHSA enrichmentGHSA-c2f5-jxjv-2hh8 · GitHub severity LOW
  15. 2026-11-01 07:12 UTCEchelonGraph re-scored
  16. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  17. 2026-10-31 09:33 UTCEchelonGraph re-scored
  18. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  19. 2026-10-30 11:56 UTCEchelonGraph re-scored
  20. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  21. 2026-10-28 16:41 UTCEchelonGraph re-scored
  22. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  23. 2026-10-27 19:02 UTCEchelonGraph re-scored
  24. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  25. 2026-10-26 21:24 UTCEchelonGraph re-scored
  26. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  27. 2026-10-25 16:58 UTCEchelonGraph re-scored
  28. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  29. 2026-10-25 00:00 UTCEchelonGraph re-scored
  30. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  31. 2026-10-24 02:22 UTCEchelonGraph re-scored
  32. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  33. 2026-10-23 04:43 UTCEchelonGraph re-scored
  34. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  35. 2026-10-22 07:02 UTCEchelonGraph re-scored
  36. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  37. 2026-10-21 09:21 UTCEchelonGraph re-scored
  38. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  39. 2026-10-20 11:44 UTCEchelonGraph re-scored
  40. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.8% · 57th percentile
  41. 2026-10-19 13:49 UTCEchelonGraph re-scored
  42. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  43. 2026-10-18 06:53 UTCEchelonGraph re-scored
  44. 2026-10-17 18:16 UTCEchelonGraph re-scored
  45. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  46. 2026-10-16 20:36 UTCEchelonGraph re-scored
  47. 2026-10-16 16:37 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  48. 2026-10-15 17:56 UTCEchelonGraph re-scored
  49. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  50. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  51. 2026-10-14 11:48 UTCEchelonGraph re-scored
  52. 2026-10-13 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  53. 2026-10-12 17:40 UTCEchelonGraph re-scored
  54. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  55. 2026-10-11 21:06 UTCEchelonGraph re-scored
  56. 2026-10-11 15:58 UTCEchelonGraph re-scored
  57. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  58. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  59. 2026-10-10 09:33 UTCOSV refresh
  60. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  61. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  62. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  63. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  64. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  65. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  66. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  67. 2026-10-02 16:19 UTCEchelonGraph re-scored
  68. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  69. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  70. 2026-09-29 15:18 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  71. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  72. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  73. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.8% · 56th percentile
  74. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.8% · 55th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2024-51745?
CVE-2024-51745 is a critical-severity vulnerability; its CVE record was published on November 5, 2024. Wasmtime is a fast and secure runtime for WebAssembly. Wasmtime's filesystem sandbox implementation on Windows blocks access to special device filenames such as "COM1", "COM2", "LPT0", "LPT1", and so on, however it did not block access to the special device filenames which use superscript digits,…
When was the CVE record for CVE-2024-51745 published?
The CVE record for CVE-2024-51745 was published on November 5, 2024. 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 September 4, 2025; the record at its source may have been updated since.
Is CVE-2024-51745 actively exploited?
CVE-2024-51745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-51745?
CVE-2024-51745 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2024-51745?
A fix for CVE-2024-51745 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-51745 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-2024-51745

Explore →

Is Your Infrastructure Affected by CVE-2024-51745?

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

Book a Demo →Browse All CVEs