Answer in brief
CVE-2026-32685 records a Medium severity (CVSS 4.6) vulnerability in Path Traversal in gleam docs build via documentation.pages Allows Arbitrary File Read and Write. The current sources do not mark it as known exploited. The current feed maps Gleam/Gleam (generic), Gleam/Gleam (generic), Gleam/Gleam (generic), Gleam/gleam-lang/gleam (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Gleam/Gleam (generic), Gleam/Gleam (generic), Gleam/Gleam (generic), Gleam/gleam-lang/gleam (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Gleam/Gleamgeneric | >=1.16.0 <1.17.0 || >=61ed8deb6572b5591ad17d6302c1a38607522f16 <81570611906b6b0039c948037094d09a68700f3a | 1.17.0, 81570611906b6b0039c948037094d09a68700f3a |
| Gleam/Gleamgeneric | >=v1.16.0-elixir <v1.17.0-elixir || >=v1.16.0-erlang <v1.17.0-erlang || >=v1.16.0-node <v1.17.0-node || >=v1.16.0-node-slim <v1.17.0-node-slim || >=v1.16.0-elixir-slim <v1.17.0-elixir-slim || >=v1.16.0-erlang-slim <v1.17.0-erlang-slim || >=v1.16.0-erlang-alpine <v1.17.0-erlang-alpine || >=v1.16.0-elixir-alpine <v1.17.0-elixir-alpine || >=v1.16.0-node-alpine <v1.17.0-node-alpine || >=v1.16.0-scratch <v1.17.0-scratch | v1.17.0-elixir, v1.17.0-erlang, v1.17.0-node, v1.17.0-node-slim, v1.17.0-elixir-slim, v1.17.0-erlang-slim, v1.17.0-erlang-alpine, v1.17.0-elixir-alpine, v1.17.0-node-alpine, v1.17.0-scratch |
| Gleam/Gleamgeneric | >=1.16.0 <1.17.0 | 1.17.0 |
| Gleam/gleam-lang/gleamgeneric | >=1.16.0 <1.17.0 || >=61ed8deb6572b5591ad17d6302c1a38607522f16 <81570611906b6b0039c948037094d09a68700f3a | 1.17.0, 81570611906b6b0039c948037094d09a68700f3a |
| Gleam/gleam-lang/gleamgeneric | >=v1.16.0-elixir <v1.17.0-elixir || >=v1.16.0-erlang <v1.17.0-erlang || >=v1.16.0-node <v1.17.0-node || >=v1.16.0-node-slim <v1.17.0-node-slim || >=v1.16.0-elixir-slim <v1.17.0-elixir-slim || >=v1.16.0-erlang-slim <v1.17.0-erlang-slim || >=v1.16.0-erlang-alpine <v1.17.0-erlang-alpine || >=v1.16.0-elixir-alpine <v1.17.0-elixir-alpine || >=v1.16.0-node-alpine <v1.17.0-node-alpine || >=v1.16.0-scratch <v1.17.0-scratch | v1.17.0-elixir, v1.17.0-erlang, v1.17.0-node, v1.17.0-node-slim, v1.17.0-elixir-slim, v1.17.0-erlang-slim, v1.17.0-erlang-alpine, v1.17.0-elixir-alpine, v1.17.0-node-alpine, v1.17.0-scratch |
Published upstream
Jun 2, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.