Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-24116: Wasmtime segfault or unused out-of-sandbox load with f64.copysign operator on x86-64

Noroxi assessment

Priority: Monitor (action score 16/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
  • Fixed version: wasmtime (crates.io) 36.0.5, 40.0.3, 41.0.1; rust-wasmtime (Debian:14) 36.0.5+dfsg-1.

Low priority for now. Upgrade to wasmtime (crates.io) 36.0.5, 40.0.3, 41.0.1; rust-wasmtime (Debian:14) 36.0.5+dfsg-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Wasmtime is a runtime for WebAssembly. Starting in version 29.0.0 and prior to version 36.0.5, 40.0.3, and 41.0.1, on x86-64 platforms with AVX, Wasmtime's compilation of the `f64.copysign` WebAssembly instruction with Cranelift may load 8 more bytes than is necessary. When signals-based-traps are disabled this can result in a uncaught segfault due to loading from unmapped guard pages. With guard pages disabled it's possible for out-of-sandbox data to be loaded, but unless there is another bug in Cranelift this data is not visible to WebAssembly guests. Wasmtime 36.0.5, 40.0.3, and 41.0.1 have been released to fix this issue. Users are recommended to upgrade to the patched versions of Wasmtime. Other affected versions are not patched and users should updated to supported major version instead. This bug can be worked around by enabling signals-based-traps. While disabling guard pages can be a quick fix in some situations, it's not recommended to disabled guard pages as it is a key defense-in-depth measure of Wasmtime.

MediumCVSS 4.1 · v4.0—No exploit Fix available
Published
Jan 27, 2026
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile

Report tools

JSON

Action score

16

Monitor

Low priority for now.

CVSS
16 / 40 · 4.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
4.1
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-24116

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for bytecodealliance records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
bytecodealliancewasmtime

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • bytecodealliance wasmtime29.0.0 and later · before 36.0.5
  • bytecodealliance wasmtime40.0.0 and later · before 40.0.3
  • bytecodealliance wasmtime41.0.0 and later · before 41.0.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • bytecodealliance wasmtime

    • >= 29.0.0, < 36.0.5, >= 37.0.0, < 40.0.3, = 41.0.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
crates.iowasmtimefrom 29.0.0 · before 36.0.536.0.5
crates.iowasmtimefrom 37.0.0 · before 40.0.340.0.3
crates.iowasmtimefrom 41.0.0 · before 41.0.141.0.1
Debian:14rust-wasmtimebefore 36.0.5+dfsg-136.0.5+dfsg-1

Same product

bytecodealliance: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-115893Wasmtime: Cranelift backend on aarch64 can jump to incorrect target on large Wasm `br_table` instruction
    39Monitor
  • CVE-2026-115889Wasmtime: Bit-packing in Cranelift compiler causes silent overflow and miscompilation
    39Monitor
  • CVE-2022-39394wasmtime_trap_code C API function has out of bounds write vulnerability
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-62711Oct 24, 2025 · Wasmtime vulnerable to segfault when using component resources
    8Monitor
  • ← EarlierCVE-2025-64345Nov 12, 2025 · Wasmtime provides unsound API access to a WebAssembly shared linear memory
    7Monitor
  • Later →CVE-2026-27195Feb 24, 2026 · Wasmtime is vulnerable to panic when dropping a `[Typed]Func::call_async` future
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
crates.io:wasmtime36.0.5Package registry (OSV)
crates.io:wasmtime40.0.3Package registry (OSV)
crates.io:wasmtime41.0.1Package registry (OSV)
debian:rust-wasmtime36.0.5+dfsg-1 · Debian:14Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-3497172 days apartWasmtime miscompiled guest heap access enables sandbox escape on aarch64 Cranelift
    36Monitor
  • CVE-2026-3498772 days apartWasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access
    36Monitor
  • CVE-2026-3494172 days apartWasmtime has a Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding
    27Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
A
Scope
X

Weakness class (CWE)

CWE-125 · Out-of-bounds Read

CVSS vector

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records