Advisory record · GHSA-55f3-3qvg-8pv5

Symlink bypasses filesystem sandbox

CVSS 2.9 LowEPSS 0.0020 · 9th percentile

Published by the GitHub Advisory Database at 7 Jun 2024, 19:40 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
wasmercrates.io<=4.3.1No fixed version yet
Identifiers
GHSA-55f3-3qvg-8pv5 · CVE-2024-38358
Weakness (CWE)
CWE-22
Published
7 Jun 2024
Updated
10 Sept 2026

Machine-written summary

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

Wasmer, versions up to and including 4.3.1, has a sandbox escape: when a directory preopened for a WASI program contains a symlink pointing outside it, the program can follow that link to reach host files. The source says this needs the caller to set both the create and write rights on the open request, and a program that creates an outside-pointing symlink and then opens it can crash the runtime. No fixed version is listed.

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
2.9 Low 3.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0020, the 9th percentile, on 19 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.