CVE-2023-41880 | Miscompilation of wasm `i64x2.shr_s` instruction with constant input on x86_64

Wasmtime is a standalone runtime for WebAssembly. Wasmtime versions from 10.0.0 to versions 10.02, 11.0.2, and 12.0.1 contain a miscompilation of the WebAssembly `i64x2.shr_s` instruction on x86_64 platforms when the shift amount is a constant value that is larger than 32. Only x86_64 is affected so all other targets are not affected by this. The miscompilation results in the instruction producing an incorrect result, namely the low 32-bits of the second lane of the vector are derived from the low 32-bits of the second lane of the input vector instead of the high 32-bits. The primary impact of this issue is that any WebAssembly program using the `i64x2.shr_s` with a constant shift amount larger than 32 may produce an incorrect result. This issue is not an escape from the WebAssembly sandbox. Execution of WebAssembly guest programs will still behave correctly with respect to memory sandboxing and isolation from the host. Wasmtime considers non-spec-compliant behavior as a security issue nonetheless. This issue was discovered through fuzzing of Wasmtime's code generator Cranelift. Wasmtime versions 10.0.2, 11.0.2, and 12.0.2 are all patched to no longer have this miscompilation. This issue only affects x86_64 hosts and the only workaround is to either scan for this pattern in wasm modules which is nontrivial or to disable the SIMD proposal for WebAssembly. Users prior to 10.0.0 are unaffected by this vulnerability.

Published: 2023-09-15 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-41880 is rated Low Risk (24.7/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.60%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-41880

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.18% 0.60% +0.42%
2 2025-11-21 0.53% 0.18% -0.35%
3 2025-11-18 — 0.53% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-41880

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.2 3.1 LOW
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 0.7 1.4 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]

Weakness enumeration for CVE-2023-41880

GitHub Security Advisory for CVE-2023-41880

GHSA-gw5p-q8mj-p7gh · Severity: low · Ecosystem: rust — Miscompilation of wasm `i64x2.shr_s` instruction with constant input on x86_64

OS Trackers for CVE-2023-41880

vendor priority summary link
debian not yet assigned CVE-2023-41880 not yet assigned priority: Debian including 1 source packages (rust-wasmtime), 3 status rows across 3 suites (forky, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2023-41880
ubuntu medium CVE-2023-41880 medium priority: Ubuntu including 1 source packages (rust-wasmtime), 6 status rows across 6 suites (focal, jammy, noble, oracular, plucky, upstream): not-affected 3, DNE 2, released 1. https://ubuntu.com/security/CVE-2023-41880

Affected software / configurations for CVE-2023-41880

Vendor Product Version Raw CPE
bytecodealliance wasmtime >= 10.0.0, < 10.0.2 cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:rust:x64:*
bytecodealliance wasmtime >= 11.0.0, < 11.0.2 cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:rust:x64:*
bytecodealliance wasmtime >= 12.0.0, < 12.0.2 cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:rust:x64:*

References for CVE-2023-41880

cvelogic Threat Intelligence