CVE-2026-34942: Wasmtime panics when transcoding misaligned utf-16 strings
Noroxi assessment
Priority: Monitor (action score 23/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.36% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
- Fixed version: bytecodealliance wasmtime 24.0.7.
Low priority for now. Upgrade to bytecodealliance wasmtime 24.0.7 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. Prior to 24.0.7, 36.0.7, 42.0.2, and 43.0.1, Wasmtime's implementation of transcoding strings into the Component Model's utf16 or latin1+utf16 encodings improperly verified the alignment of reallocated strings. This meant that unaligned pointers could be passed to the host for transcoding which would trigger a host panic. This panic is possible to trigger from malicious guests which transfer very specific strings across components with specific addresses. Host panics are considered a DoS vector in Wasmtime as the panic conditions are controlled by the guest in this situation. This vulnerability is fixed in 24.0.7, 36.0.7, 42.0.2, and 43.0.1.
- Published
- Apr 9, 2026
- Updated
- Oct 26, 2026
- EPSS
- 0.3% · 31th percentile
- CWE
- CWE-129
Report tools
Action score
23
Low priority for now.
- CVSS
- 23 / 40 · 5.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 5.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| bytecodealliance | wasmtime | cpe:2.3:a:bytecodealliance:wasmtime |
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
- < 24.0.7, >= 25.0.0, < 36.0.7, >= 37.0.0, < 42.0.2, >= 43.0.0, < 44.0.1affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- bytecodealliance wasmtimebefore 24.0.7
- bytecodealliance wasmtime25.0.0 and later · before 36.0.7
- bytecodealliance wasmtime37.0.0 and later · before 42.0.2
- bytecodealliance wasmtime43.0.0 and later · before 43.0.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| crates.io | wasmtime | from 0.0.0-0 · before 24.0.7 | 24.0.7 |
| crates.io | wasmtime | from 25.0.0 · before 36.0.7 | 36.0.7 |
| crates.io | wasmtime | from 37.0.0 · before 42.0.2 | 42.0.2 |
| crates.io | wasmtime | from 43.0.0 · before 43.0.1 | 43.0.1 |
| crates.io | wasmtime | before 24.0.7 | 24.0.7 |
| Debian:13 | rust-wasmtime | from 0 | — |
| Debian:14 | rust-wasmtime | before 36.0.7+dfsg-1 | 36.0.7+dfsg-1 |
| openSUSE:Tumbleweed | zed | before 1.24.2-1.1 | 1.24.2-1.1 |
Same product
bytecodealliance: all recordsOther 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` instruction39Monitor
- CVE-2026-115889Wasmtime: Bit-packing in Cranelift compiler causes silent overflow and miscompilation39Monitor
- CVE-2022-39394wasmtime_trap_code C API function has out of bounds write vulnerability39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-27572Feb 24, 2026 · Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance27Monitor
- ← EarlierCVE-2026-34941Apr 9, 2026 · Wasmtime has a Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding27Monitor
- Later →CVE-2026-34943Apr 9, 2026 · Wasmtime panics when lifting `flags` component value22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| bytecodealliance wasmtime | 24.0.7 · description | Vendor (CNA) |
| crates.io:wasmtime | 24.0.7 | Package registry (OSV) |
| crates.io:wasmtime | 36.0.7 | Package registry (OSV) |
| crates.io:wasmtime | 42.0.2 | Package registry (OSV) |
| crates.io:wasmtime | 43.0.1 | Package registry (OSV) |
| debian:rust-wasmtime | 36.0.7+dfsg-1 · Debian:14 | Package registry (OSV) |
| opensuse:zed | 1.24.2-1.1 · openSUSE:Tumbleweed | Package 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.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-119143203 days apartWasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 Panic via Zero-Length Stream Writes23Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-129 · Improper Validation of Array IndexCVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/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.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.