Skip to content
Threat Brief

← All advisories

CVE-2026-32685

Medium 4.6No known exploitationFix available

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

Record last updated

CVSS score

4.6

Medium on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 14% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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/ / 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 before 1.17.0.

Weakness: CWE-22

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
* Avoid running gleam docs build on untrusted projects * Review documentation.pages entries in gleam.toml before generating documentation * Run documentation generation in a restricted or isolated environment (e.g. containers) Source (opens in a new tab)
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
GleamGleamfrom 1.16.0 before 1.17.01.17.0CVE Program
GleamGleamfrom 61ed8deb6572b5591ad17d6302c1a38607522f16 before 81570611906b6b0039c948037094d09a68700f3a81570611906b6b0039c948037094d09a68700f3aCVE Program
GleamGleamfrom v1.16.0-elixir before v1.17.0-elixirv1.17.0-elixirCVE Program
GleamGleamfrom v1.16.0-elixir-alpine before v1.17.0-elixir-alpinev1.17.0-elixir-alpineCVE Program
GleamGleamfrom v1.16.0-elixir-slim before v1.17.0-elixir-slimv1.17.0-elixir-slimCVE Program
GleamGleamfrom v1.16.0-erlang before v1.17.0-erlangv1.17.0-erlangCVE Program
GleamGleamfrom v1.16.0-erlang-alpine before v1.17.0-erlang-alpinev1.17.0-erlang-alpineCVE Program
GleamGleamfrom v1.16.0-erlang-slim before v1.17.0-erlang-slimv1.17.0-erlang-slimCVE Program
GleamGleamfrom v1.16.0-node before v1.17.0-nodev1.17.0-nodeCVE Program
GleamGleamfrom v1.16.0-node-alpine before v1.17.0-node-alpinev1.17.0-node-alpineCVE Program
GleamGleamfrom v1.16.0-node-slim before v1.17.0-node-slimv1.17.0-node-slimCVE Program
GleamGleamfrom v1.16.0-scratch before v1.17.0-scratchv1.17.0-scratchCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references