Skip to main content
No exploitation reportedFix available

CVE-2026-34941

No exploitation reported by the sources we read.

  • Published2026-04-09
  • Fixed in43.0.1 · 42.0.2 · 36.0.7 · 24.0.7
  • WeaknessCWE-125

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Wasmtime is a runtime for WebAssembly. Prior to 24.0.7, 36.0.7, 42.0.2, and 43.0.1, Wasmtime contains a vulnerability where when transcoding a UTF-16 string to the latin1+utf16 component-model encoding it would incorrectly validate the byte length of the input string when performing a bounds check. Specifically the number of code units were checked instead of the byte length, which is twice the size of the code units. This vulnerability can cause the host to read beyond the end of a WebAssembly's linear memory in an attempt to transcode nonexistent bytes. In Wasmtime's default configuration this will read unmapped memory on a guard page, terminating the process with a segfault. Wasmtime can be configured, however, without guard pages which would mean that host memory beyond the end of linear memory may be read and interpreted as UTF-16. A host segfault is a denial-of-service vulnerability in Wasmtime, and possibly being able to read beyond the end of linear memory is additionally a vulnerability. Note that reading beyond the end of linear memory requires nonstandard configuration of Wasmtime, specifically with guard pages disabled. This vulnerability is fixed in 24.0.7, 36.0.7, 42.0.2, and 43.0.1.

Timeline

dates in UTC
  1. 2026-04-0919:16CVE publishedNVD

Versions per branch

NVD · OSV
Bytecodealliance wasmtime
BranchAffectedFixed in
43.0≥ 43.0.0, < 43.0.143.0.1
42.0≥ 37.0.0, < 42.0.242.0.2
36.0≥ 25.0.0, < 36.0.736.0.7
24.0< 24.0.724.0.7
24.0≥ 0.0.0-0, < 24.0.724.0.7

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • bytecodealliance wasmtime
    Affected
    • = < 24.0.7no fix stated
    • = >= 25.0.0, < 36.0.7no fix stated
    • = >= 37.0.0, < 42.0.2no fix stated
    • = >= 43.0.0, < 44.0.1no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-04-09

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • rust-wasmtimeUbuntu:26.10all versions · no fixed version listed
  • rust-wasmtimeUbuntu:26.04:LTSall versions · no fixed version listed
  • rust-wasmtimeUbuntu:25.10all versions · no fixed version listed
  • rust-wasmtimeUbuntu:24.04:LTSall versions · no fixed version listed
  • rust-wasmtimeDebian:14all versions · fixed in 36.0.7+dfsg-1
  • rust-wasmtimeDebian:13all versions · no fixed version listed
  • tree-sitteropenSUSE:Tumbleweedall versions · fixed in 0.26.8-2.1
  • washWolfiall versions · no fixed version listed

10 more package ranges on OSV.dev

Vendor advisories

  • CVE-2026-34941 Red Hat Product Security1 known affected

    wasmtime: Wasmtime: Denial of Service and potential information disclosure via incorrect UTF-16 string validation

    redhat-user-workloads/rhcl-1-3-wasm-shim as a component of Red Hat Connectivity Link 1

Full record on NVD

Fix

  1. Update Bytecodealliance wasmtime to 43.0.1 · 42.0.2 · 36.0.7 · 24.0.7
  2. Workaround from the vendor Red Hat Product Security CVE-2026-34941 · 1 productMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
  3. No fix available, says the vendor Red Hat Product Security CVE-2026-34941 · 1 productAffected

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2026-04-10
  • CNACVSS 4.06.9known since 2026-10-27
  • NVDCVSS 3.18.1read 2026-10-27
  • CNAweakness (CWE)CWE-125known since 2026-10-27
  • FIRST EPSSEPSS score0.4 %2026-11-17
  • OSVaffected packages—
  • GitHub AdvisoriesadvisoryMODERATE2026-04-09

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/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
Published
2026-04-09
Last Modified
2026-10-26
NVD status
Analyzed
GitHub Advisory
GHSA-hx6p-xpx3-jvvv

Frequently asked questions

What is CVE-2026-34941?

Wasmtime is a runtime for WebAssembly. Prior to 24.0.7, 36.0.7, 42.0.2, and 43.0.1, Wasmtime contains a vulnerability where when transcoding a UTF-16 string to the latin1+utf16 component-model encoding it would incorrectly validate the byte length of the input string when performing a bounds check. Specifically the number of code units were checked instead of the byte length, which is twice the size of the code units. This vulnerability can cause the host to read beyond the end of a WebAssembly's linear memory in an attempt to transcode nonexistent bytes. In Wasmtime's default configuration this will read unmapped memory on a guard page, terminating the process with a segfault. Wasmtime can be configured, however, without guard pages which would mean that host memory beyond the end of linear memory may be read and interpreted as UTF-16. A host segfault is a denial-of-service vulnerability in Wasmtime, and possibly being able to read beyond the end of linear memory is additionally a vulnerability. Note that reading beyond the end of linear memory requires nonstandard configuration of Wasmtime, specifically with guard pages disabled. This vulnerability is fixed in 24.0.7, 36.0.7, 42.0.2, and 43.0.1.

Is CVE-2026-34941 actively exploited?

Active exploitation of CVE-2026-34941 has not been confirmed. Its EPSS score was 0.4% on 2026-11-17, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-34941?

CVE-2026-34941 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H.

Running wasmtime? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record