Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. A reference of the record is tagged as an exploit. CISA's SSVC rates its exploitation: a proof of concept is public.

Show the exploits1

Timeline

  1. ID reserved

    By EEF

  2. · 3 months later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-32685, by who scored it
Scored byCVSSScoreVector
EEFCNA (assigner)4.0Medium4.6CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
NVDNVD · Deferred4.0Medium4.6CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 4.6.

Affected products

  • Gleam · Gleam

    • affected 1.16.0 – < 1.17.0
  • Gleam · Gleam

    • affected v1.16.0-elixir – < v1.17.0-elixir
    • affected v1.16.0-erlang – < v1.17.0-erlang
    • affected v1.16.0-node – < v1.17.0-node
    • affected v1.16.0-node-slim – < v1.17.0-node-slim
    • affected v1.16.0-elixir-slim – < v1.17.0-elixir-slim
    • affected v1.16.0-erlang-slim – < v1.17.0-erlang-slim
    • affected v1.16.0-erlang-alpine – < v1.17.0-erlang-alpine
    • affected v1.16.0-elixir-alpine – < v1.17.0-elixir-alpine
    • affected v1.16.0-node-alpine – < v1.17.0-node-alpine
    • affected v1.16.0-scratch – < v1.17.0-scratch
  • Gleam · Gleam

    • affected 61ed8deb6572b5591ad17d6302c1a38607522f16 – < 81570611906b6b0039c948037094d09a68700f3a

What to do

Workaround: * 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)

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-32685 badge
[![CVE-2026-32685](https://cveledger.app/badge/CVE-2026-32685.svg)](https://cveledger.app/cve/CVE-2026-32685)

Record last updated .