CVE-2026-32685
Published: Jun 2, 2026
Modified: Jun 2, 2026
Description
Path traversal vulnerability in Gleam's handling of custom documentation pages allows arbitrary file read and file write outside the intended documentation output directory. The documentation.pages entries from gleam.toml are incorporated into filesystem paths without sufficient validation or confinement to the intended project and documentation output directories. The documentation.pages[].path field can be used to write generated documentation files outside the intended build/dev/docs/<package>/ output directory. The documentation.pages[].source field can be used to read files outside the project directory and embed their contents into generated documentation output. An attacker who can convince a victim to run gleam docs build on an untrusted project, or with untrusted gleam.toml content, can cause local files readable by the victim to be included in generated documentation artifacts, and can cause generated documentation files to be written outside the intended docs output directory. This issue affects Gleam from 1.16.0 until 1.17.0.
| Vendor | Product | Versions |
|---|---|---|
Gleam | Gleam | affected 1.16.0 - < 1.17.0 |
Gleam | Gleam | affected 1.16.0 - < 1.17.0affected 61ed8deb6572b5591ad17d6302c1a38607522f16 - < 81570611906b6b0039c948037094d09a68700f3a |
Gleam | Gleam | affected v1.16.0-elixir - < v1.17.0-elixiraffected v1.16.0-erlang - < v1.17.0-erlangaffected v1.16.0-node - < v1.17.0-nodeaffected v1.16.0-node-slim - < v1.17.0-node-slimaffected v1.16.0-elixir-slim - < v1.17.0-elixir-slim+5 more versions |
Weaknesses (CWE)
References
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now