Local file disclosure via symlink-following package export
Published Jun 2, 2026 · Updated Jun 2, 2026
Link following in Gleam before 1.17.0 allows attackers to disclose local files through a crafted symlink during Hex package export. The gleam_files, native_files, and private_files helpers follow links while collecting src and priv entries, and add_path_to_tar archives each resolved target without confirming that it remains under the project root. Exploitation requires write access to the repository and a maintainer or CI job to run a publish or export command, after which package recipients can read files available to that publisher.
Summary
What happened
Link following in Gleam before 1.17.0 allows attackers to disclose local files through a crafted symlink during Hex package export. The gleam_files, native_files, and private_files helpers follow links while collecting src and priv entries, and add_path_to_tar archives each resolved target without confirming that it remains under the project root. Exploitation requires write access to the repository and a maintainer or CI job to run a publish or export command, after which package recipients can read files available to that publisher.
The record
- CVE
- CVE-2026-42795
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- Gleam
- Product
- Gleam
- Classifications
- CWE-200, CWE-59, CAPEC-132, T1204.002
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.10.0-rc1 <1.17.0
- Affected versionversion=c82a2d83bd0c06cafdc196820deb3f89a9b3ff7c <6435a5528b9ae0449e2f32be579641ec485f6866
- Affected versionversion=v0.10.0-rc1-elixir-alpine <v1.17.0-elixir-alpine
- Affected versionversion=v0.10.0-rc1-elixir-slim <v1.17.0-elixir-slim
- Affected versionversion=v0.10.0-rc1-elixir <v1.17.0-elixir
- Affected versionversion=v0.10.0-rc1-erlang-alpine <v1.17.0-erlang-alpine
- Affected versionversion=v0.10.0-rc1-erlang-slim <v1.17.0-erlang-slim
- Affected versionversion=v0.10.0-rc1-erlang <v1.17.0-erlang
- Affected versionversion=v0.10.0-rc1-node-alpine <v1.17.0-node-alpine
- Affected versionversion=v0.10.0-rc1-node-slim <v1.17.0-node-slim
- Affected versionversion=v0.10.0-rc1-node <v1.17.0-node
- Affected versionversion=v0.10.0-rc1-scratch <v1.17.0-scratch
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream Hex tarball symlink proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo