CVE-2026-32685

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine without logging in, but needs a user to act. Limited direct impact.

Exploit odds

0.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-06-02 14:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-06 22:10 UTC Last updatedMost recent change to the record

Details

Published

2026-06-02 14:16 UTC

Last modified

2026-10-06 22:10 UTC

Exploit probability

0.2% · EPSS, next 30 days

Weakness

CWE-22 · Path traversal

Record status

Deferred

Attack profile CVSS 4.0 · 4.6

Attack vector

Local

Complexity

Low

Attack requirements

None

Privileges needed

None

User interaction

Active

Confidentiality

Low

Integrity

Low

Availability

None