5.1
/ 10
MEDIUM
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
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.
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.
Basic Information
ID
CVE-2026-42795
Source
EEF
Published
Jun 2, 2026 at 13:41
Affected Product
Vendor
Gleam
Product
Gleam
Version
0.10.0-rc1
Affected Versions
Gleam Gleam 0.10.0-rc1
Gleam Gleam 0.10.0-rc1
Gleam Gleam c82a2d83bd0c06cafdc196820deb3f89a9b3ff7c
Gleam Gleam v0.10.0-rc1-elixir
Gleam Gleam v0.10.0-rc1-erlang
Gleam Gleam v0.10.0-rc1-node
Gleam Gleam v0.10.0-rc1-node-slim
Gleam Gleam v0.10.0-rc1-elixir-slim
Gleam Gleam v0.10.0-rc1-erlang-slim
Gleam Gleam v0.10.0-rc1-erlang-alpine
Gleam Gleam v0.10.0-rc1-elixir-alpine
Gleam Gleam v0.10.0-rc1-node-alpine
Gleam Gleam v0.10.0-rc1-scratch
Gleam Gleam 0.10.0-rc1
Gleam Gleam c82a2d83bd0c06cafdc196820deb3f89a9b3ff7c
Gleam Gleam v0.10.0-rc1-elixir
Gleam Gleam v0.10.0-rc1-erlang
Gleam Gleam v0.10.0-rc1-node
Gleam Gleam v0.10.0-rc1-node-slim
Gleam Gleam v0.10.0-rc1-elixir-slim
Gleam Gleam v0.10.0-rc1-erlang-slim
Gleam Gleam v0.10.0-rc1-erlang-alpine
Gleam Gleam v0.10.0-rc1-elixir-alpine
Gleam Gleam v0.10.0-rc1-node-alpine
Gleam Gleam v0.10.0-rc1-scratch