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.
Metrics
Affected Vendors & Products
| Vendors | Products |
|---|---|
| Gleam-lang |
|
No data.
No data.
No data.
References
History
Tue, 02 Jun 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 02 Jun 2026 14:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Path Traversal in gleam docs build via documentation.pages Allows Arbitrary File Read and Write | |
| First Time appeared |
Gleam-lang
Gleam-lang gleam |
|
| Weaknesses | CWE-22 | |
| CPEs | cpe:2.3:a:gleam-lang:gleam:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Gleam-lang
Gleam-lang gleam |
|
| References |
|
|
| Metrics |
cvssV4_0
|
MITRE
Status: PUBLISHED
Assigner: EEF
Published:
Updated: 2026-06-02T15:06:40.363Z
Reserved: 2026-03-13T09:12:14.474Z
Link: CVE-2026-32685
Vulnrichment
Updated: 2026-06-02T15:05:46.263Z
NVD
Status : Deferred
Published: 2026-06-02T14:16:50.610
Modified: 2026-06-02T14:46:08.900
Link: CVE-2026-32685
Redhat
No data.
OpenCVE Enrichment
No data.