CVE-2026-32685

Path Traversal in gleam docs build via documentation.pages Allows Arbitrary File Read and Write

MEDIUM
4.6
CVSS Score
Published: June 2, 2026 at 01:41 PM UTC
Updated: October 6, 2026 at 10:10 PM UTC
2 products affected across 2 vendorsGleamGleam

Using Gleam by Gleam?

Get instant alerts when new vulnerabilities affect Gleam - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.6
Exploit prediction
EPSS 0.2%
SSVC
PoC

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.16.0 ≤ v < 1.17.0
Affected range stops below 1.17.0, so it looks safe — our inference, not a vendor statement
1.16.0 ≤ v < 1.17.0v1.16.0-elixir ≤ v < v1.17.0-elixirv1.16.0-elixir-alpine ≤ v < v1.17.0-elixir-alpinev1.16.0-elixir-slim ≤ v < v1.17.0-elixir-slimv1.16.0-erlang ≤ v < v1.17.0-erlangv1.16.0-erlang-alpine ≤ v < v1.17.0-erlang-alpinev1.16.0-erlang-slim ≤ v < v1.17.0-erlang-slimv1.16.0-node ≤ v < v1.17.0-nodev1.16.0-node-alpine ≤ v < v1.17.0-node-alpinev1.16.0-node-slim ≤ v < v1.17.0-node-slimv1.16.0-scratch ≤ v < v1.17.0-scratch1.16.01.16.0-elixir1.16.0-elixir-alpine1.16.0-elixir-slim1.16.0-erlang1.16.0-erlang-alpine1.16.0-erlang-slim1.16.0-node1.16.0-node-alpine1.16.0-node-slim1.16.0-scratch61ed8deb6572b5591ad17d6302c1a38607522f16
Vendor states this is fixed in 81570611906b6b0039c948037094d09a68700f3a (fixed)
Affected range stops below 1.17.0, so it looks safe — our inference, not a vendor statement
Affected range stops below v1.17.0-elixir, so it looks safe — our inference, not a vendor statement
Affected range stops below v1.17.0-elixir-alpine, so it looks safe — our inference, not a vendor statement
Affected range stops below v1.17.0-elixir-slim, so it looks safe — our inference, not a vendor statement
Affected range stops below v1.17.0-erlang, so it looks safe — our inference, not a vendor statement
Affected range stops below v1.17.0-erlang-alpine, so it looks safe — our inference, not a vendor statement
Affected range stops below v1.17.0-erlang-slim, so it looks safe — our inference, not a vendor statement
Affected range stops below v1.17.0-node, so it looks safe — our inference, not a vendor statement
Affected range stops below v1.17.0-node-alpine, so it looks safe — our inference, not a vendor statement
Affected range stops below v1.17.0-node-slim, so it looks safe — our inference, not a vendor statement
Affected range stops below v1.17.0-scratch, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

4.6MEDIUMEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-22

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card