Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.2

Miscompilation of wasm i64x2.shr_s instruction with constant input on x86_64

CVE-2023-41880GHSA-gw5p-q8mj-p7gh

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (wasmtime 12.0.2, 11.0.2, 10.0.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • crates.io wasmtime

    Affected
    >= 10.0.0, < 10.0.2>= 11.0.0, < 11.0.2>= 12.0.0, < 12.0.2
    Fixed in
    11.0.2, 10.0.2, 12.0.2

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
2.2 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N
EPSS
  • CVE-2023-41880: 0.67% estimated exploitation activity in the next 30 days; percentile 52.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact Wasmtime versions from 10.0.0 to 12.0.1 contain a miscompilation of the WebAssembly i64x2.shrs instruction on x8664 platforms when the shift amount is a constant value that is larger than 32. Only x8664 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.shrs 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-gw5p-q8mj-p7gh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-41880

Advisory: Miscompilation of wasm `i64x2.shr_s` instruction with constant input on x86_64
IDs: CVE-2023-41880, GHSA-gw5p-q8mj-p7gh
Record: https://patchnext.com/advisories/cve-2023-41880 (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: wasmtime 12.0.2, 11.0.2, 10.0.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io wasmtime: affected >= 10.0.0, < 10.0.2; >= 11.0.0, < 11.0.2; >= 12.0.0, < 12.0.2; fixed in 11.0.2, 10.0.2, 12.0.2

## Suggested inspection (read-only)
- crates.io wasmtime: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wasmtime.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gw5p-q8mj-p7gh (GitHub-reviewed advisory GHSA-gw5p-q8mj-p7gh lists affected ranges: crates.io wasmtime >=10.0.0 =11.0.0 =12.0.0 <12.0.2)

Commands are suggestions: review each one before running it.

Loading voting…