Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Low, CVSS 2.9

Symlink bypasses filesystem sandbox

CVE-2024-38358GHSA-55f3-3qvg-8pv5

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

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 wasmer

    Affected
    <= 4.3.1
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
2.9 · CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2024-38358: 0.20% estimated exploitation activity in the next 30 days; percentile 9.94 (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.

Summary If the preopened directory has a symlink pointing outside, WASI programs can traverse the symlink and access host filesystem if the caller sets both oflags::creat and rights::fdwrite. Programs can also crash the runtime by creating a symlink pointing outside with pathsymlink and pathopening the link. Details PoC Setup a filesystem as follows. Compile this Rust snippet with wasi v0.11 (for the preview1 API). Run the compiled binary with Wasmer preopening preopen/: This should not print the contents of the outside.file. Other runtimes like Wasmtime can successfully block this call. But Wasmer prints the contents of the file.

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

    Published from ghsa record GHSA-55f3-3qvg-8pv5

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-2024-38358

Advisory: Symlink bypasses filesystem sandbox
IDs: CVE-2024-38358, GHSA-55f3-3qvg-8pv5
Record: https://patchnext.com/advisories/cve-2024-38358 (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.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io wasmer: affected <= 4.3.1

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on wasmer.
- 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-55f3-3qvg-8pv5 (GitHub-reviewed advisory GHSA-55f3-3qvg-8pv5 lists affected ranges: crates.io wasmer >=0 <=4.3.1)

Commands are suggestions: review each one before running it.

Loading voting…