Answer in brief
CVE-2026-103061 records a Medium severity (CVSS 5.9) vulnerability in Path traversal in Gleam via unvalidated package application names. The current sources do not mark it as known exploited. The current feed maps Gleam/Gleam (generic), Gleam/gleam-lang/gleam (generic), Gleam/gleam-lang/gleam (generic). 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 5.9. 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-lang/gleam (generic), Gleam/gleam-lang/gleam (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Gleam/Gleamgeneric | >=0.32.4 <1.19.2 | 1.19.2 |
| Gleam/gleam-lang/gleamgeneric | >=v0.32.4-elixir <v1.19.2-elixir || >=v0.32.4-erlang <v1.19.2-erlang || >=v0.32.4-node <v1.19.2-node || >=v0.32.4-node-slim <v1.19.2-node-slim || >=v0.32.4-elixir-slim <v1.19.2-elixir-slim || >=v0.32.4-erlang-slim <v1.19.2-erlang-slim || >=v0.32.4-erlang-alpine <v1.19.2-erlang-alpine || >=v0.32.4-elixir-alpine <v1.19.2-elixir-alpine || >=v0.32.4-node-alpine <v1.19.2-node-alpine || >=v0.32.4-scratch <v1.19.2-scratch | v1.19.2-elixir, v1.19.2-erlang, v1.19.2-node, v1.19.2-node-slim, v1.19.2-elixir-slim, v1.19.2-erlang-slim, v1.19.2-erlang-alpine, v1.19.2-elixir-alpine, v1.19.2-node-alpine, v1.19.2-scratch |
| Gleam/gleam-lang/gleamgeneric | >=d13f27ee80aae7a521d2e9433c4deaf53f892574 <* | * |
Published upstream
Oct 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 12, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 12, 2026
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in gleam-lang gleam allows a malicious package publisher to delete a directory outside the project's build directory when a developer builds a project. A Hex package release's metadata carries an app field with the release's OTP application name. Gleam reads this field from the hex.pm release API when it downloads dependencies and uses it as the package's build directory name without validating it (hex_manifest_package in compiler-cli/src/dependencies.rs, ProjectPaths::build_directory_for_package). When a dependency fails to compile, Gleam deletes that directory with remove_dir_all. hex.pm didn't restrict the field to a directory name before 2026-10-12, so a publisher could set it to a value such as ../../../../target or an absolute path. When a project depends on such a release directly or transitively and the release fails to compile, gleam build, gleam check, gleam run, gleam test or gleam export deletes the directory the name resolves to. For a pure Gleam package no publisher code runs. This issue affects gleam: from 0.32.4 before 1.19.2.
Quoted source text, attributed separately from HOL analysis.