CVE-2026-34942: Wasmtime panics when transcoding misaligned utf-16 strings

Published Apr 9, 2026
·
Updated

Impact

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.

Patches

Wasmtime 24.0.7, 36.0.7, 42.0.2, and 43.0.1 have been issued to fix this bug. Users are recommended to update to these patched versions of Wasmtime.

Workarounds

There is no workaround for this bug. Hosts are recommended to updated to a patched version of Wasmtime.

Other sources

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.

MITRE

Affected Software

8 affected componentsFixes available
rust/wasmtime=43.0.0
43.0.1
rust/wasmtime>=37.0.0<42.0.2
42.0.2
rust/wasmtime>=25.0.0<36.0.7
36.0.7
rust/wasmtime<24.0.7
24.0.7
bytecodealliance Wasmtime Rust<24.0.7
bytecodealliance Wasmtime Rust>=25.0.0<36.0.7
bytecodealliance Wasmtime Rust>=37.0.0<42.0.2
bytecodealliance Wasmtime Rust>=43.0.0<43.0.1

Event History

Apr 9, 2026
CVE Published
via MITRE·06:32 PM
Data Sourced
via MITRE·06:32 PM
DescriptionWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
Affected Software
Advisory Published
via GitHub·08:22 PM
Data Sourced
via GitHub·08:22 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-34942?

CVE-2026-34942 has a medium severity rating of 5.9 according to the CVSS score.

2

What is the impact of CVE-2026-34942?

CVE-2026-34942 can cause Wasmtime to panic when transcoding misaligned UTF-16 strings, leading to potential host panics.

3

How do I fix CVE-2026-34942?

To fix CVE-2026-34942, ensure you are using an updated version of Wasmtime that addresses the alignment verification issue.

4

Which software is affected by CVE-2026-34942?

CVE-2026-34942 affects the Wasmtime implementation in the Rust programming environment.

5

What types of vulnerabilities are associated with CVE-2026-34942?

CVE-2026-34942 is associated with out-of-bounds reads and buffer overflow vulnerabilities.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203