CVE-2026-42795 Symlink Following in Hex Package Export Allows Embedding Files Outside Project Root
Attackers with repository write access can embed sensitive local files into published packages via symlinks, exposing secrets to consumers.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-42795?
CVE-2026-42795 is a medium-severity path traversal vulnerability in Gleam, published on 2 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Official description
Symlink following vulnerability in Gleam's Hex package export allows files outside the project root to be embedded in the generated package tarball.
The file collection helpers (gleam_files, native_files, private_files) in compiler-cli/src/fs.rs use follow_links(true) when walking publishable directories such as src/ and priv/. The collected paths are added to the package archive via add_path_to_tar in compiler-cli/src/publish.rs without verifying that the resolved target remains within the project root. A symlink placed under a publishable directory will cause gleam export hex-tarball or gleam publish to embed the contents of the symlink target into the generated Hex package.
An attacker with write access to the project repository can place a symlink in src/ or priv/ pointing to an arbitrary file. When a maintainer or CI pipeline runs gleam publish or gleam export hex-tarball, local files readable by the publisher (such as secrets, tokens, or SSH keys) are silently embedded into the published package artifact.
This issue affects Gleam from 0.10.0-rc1 until 1.17.0.
Weakness: CWE-59
Which versions are affected by CVE-2026-42795?
How do I fix CVE-2026-42795?
Apply the vendor's patch.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-42795 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42795 exists.
Sources
Also known as EEF-CVE-2026-42795, GHSA-qhh5-fg4c-8gqc.