File read and write via custom-page traversal
Published Jun 2, 2026 · Updated Jun 2, 2026
Path traversal in Gleam 1.16.0 before 1.17.0 allows attackers to read local files and write generated pages via untrusted projects. The documentation generator incorporates documentation.pages[].source and .path from gleam.toml into filesystem paths without confining reads to the project root or writes to the documentation output directory. Exploitation requires a victim or automation to run gleam docs build on a project using malicious custom-page entries; exposed files are limited to those readable or writable by that process.
Summary
What happened
Path traversal in Gleam 1.16.0 before 1.17.0 allows attackers to read local files and write generated pages via untrusted projects. The documentation generator incorporates documentation.pages[].source and .path from gleam.toml into filesystem paths without confining reads to the project root or writes to the documentation output directory. Exploitation requires a victim or automation to run gleam docs build on a project using malicious custom-page entries; exposed files are limited to those readable or writable by that process.
The record
- CVE
- CVE-2026-32685
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- Gleam
- Product
- Gleam
- Classifications
- CWE-22, CAPEC-139, CAPEC-597, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
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=1.16.0 <1.17.0
- Affected versionversion=61ed8deb6572b5591ad17d6302c1a38607522f16 <81570611906b6b0039c948037094d09a68700f3a
- Affected versionversion=v1.16.0-elixir-alpine <v1.17.0-elixir-alpine
- Affected versionversion=v1.16.0-elixir-slim <v1.17.0-elixir-slim
- Affected versionversion=v1.16.0-elixir <v1.17.0-elixir
- Affected versionversion=v1.16.0-erlang-alpine <v1.17.0-erlang-alpine
- Affected versionversion=v1.16.0-erlang-slim <v1.17.0-erlang-slim
- Affected versionversion=v1.16.0-erlang <v1.17.0-erlang
- Affected versionversion=v1.16.0-node-alpine <v1.17.0-node-alpine
- Affected versionversion=v1.16.0-node-slim <v1.17.0-node-slim
- Affected versionversion=v1.16.0-node <v1.17.0-node
- Affected versionversion=v1.16.0-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
- Path traversal and arbitrary file read in gleam docs build via documentation.pagesproof 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