CVE-2024-51745Network attack vector

Windows sandbox bypass via superscript device names

Published Nov 5, 2024 · Updated Nov 5, 2024

Sandbox bypass in Wasmtime before 24.0.2, 25.0.0 through 25.0.2, and 26.0.0 allows guest OS users to access Windows devices. The cap-std Windows open primitive checks reserved device names against an incomplete list that omits names containing superscript digits. A guest must receive access to any filesystem directory; crafted COM¹ or LPT⁰ names then reach serial, parallel, USB-emulated, or mapped network devices.

CVSS severity2.3
Low
EPSS probability0.84%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sandbox bypass in Wasmtime before 24.0.2, 25.0.0 through 25.0.2, and 26.0.0 allows guest OS users to access Windows devices. The cap-std Windows open primitive checks reserved device names against an incomplete list that omits names containing superscript digits. A guest must receive access to any filesystem directory; crafted COM¹ or LPT⁰ names then reach serial, parallel, USB-emulated, or mapped network devices.

The record

CVE
CVE-2024-51745
Published
Nov 5, 2024
Updated
Nov 5, 2024
Vendor
Bytecode Alliance
Product
Wasmtime
Classifications
CWE-67, CWE-184
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Nov 5, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 5, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 24.0.2
  2. Affected versionversion=>= 25.0.0, < 25.0.3
  3. Affected versionversion== 26.0.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Bytecode Alliance · Wasmtimeversion=< 24.0.2; version=>= 25.0.0, < 25.0.3; version== 26.0.0

Published CVSS scores

10.0NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
2.3GitHub, Inc.CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-67Improper Handling of Windows Device Names
CWE-184Incomplete List of Disallowed Inputs

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo