Advisory record · GHSA-4mq4-7rw3-vm5j

Wasmer filesystem sandbox not enforced

CVSS 8.4 HighEPSS 0.0060 · 49th percentile

Published by the GitHub Advisory Database at 13 Dec 2023, 13:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
wasmer-clicrates.io>=3.0.0, <4.2.44.2.4
Identifiers
GHSA-4mq4-7rw3-vm5j · CVE-2023-51661
Weakness (CWE)
CWE-284
Published
13 Dec 2023
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Wasmer CLI versions 3.0.0 up to 4.2.4 (fixed in 4.2.4) let a Wasm program access the host filesystem outside its sandbox. An attacker who can supply a Wasm program to run on Wasmer can, for example, create files in the working directory even when the program is run without the --dir option. Upgrade wasmer-cli to 4.2.4 or later. The source gives few details on other workarounds.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.4 High 3.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0060, the 49th percentile, on 22 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:17 UTC First seen by agentprime
  2. 31 Oct 2026, 15:17 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.