Symlink Following in Hex Package Export Allows Embedding Files Outside Project Root
Gleam
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Gleam Gleam |
| No fix yet |
| Gleam Gleam |
Gleam
| Product | Affected | Fixed in |
|---|---|---|
| Gleam Gleam |
| No fix yet |
| Gleam Gleam |
≥ 0.10.0-rc1 · < 1.17.0| No fix yet |
| Gleam Gleam |
| No fix yet |
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 before 1.17.0.
From the CVE record · EEF
Gleam follows symlinks under publishable directories without checking whether their targets remain inside the project root. An attacker with write access to the project repository can add a symlink that causes a maintainer or CI pipeline running `gleam publish` or `gleam export hex-tarball` to embed readable local files in the package artifact.
Teams using Gleam versions from 0.10.0-rc1 to before 1.17.0 should check their publishing workflows.