CVE-2026-32146

Improper path validation vulnerability in the Gleam compiler's handling of git dependencies allows arbitrary file system modification during dependency download. Dependency names from gleam.toml and manifest.toml are incorporated into filesystem paths without sufficient validation or confinement to the intended dependency directory, allowing attacker-controlled paths (via relative traversal such as ../ or absolute paths) to target filesystem locations outside that directory. When resolving git dependencies (e.g. via gleam deps download), the computed path is used for filesystem operations including directory deletion and creation. This vulnerability occurs during the dependency resolution and download phase, which is generally expected to be limited to fetching and preparing dependencies within a confined directory. A malicious direct or transitive git dependency can exploit this issue to delete and overwrite arbitrary directories outside the intended dependency directory, including attacker-chosen absolute paths, potentially causing data loss. In some environments, this may be further leveraged to achieve code execution, for example by overwriting git hooks or shell configuration files. This issue affects Gleam from 1.9.0-rc1 until 1.15.4.
Configurations

Configuration 1 (hide)

cpe:2.3:a:lpil:gleam:*:*:*:*:*:*:*:*

History

21 May 2026, 20:14

Type Values Removed Values Added
References () https://cna.erlef.org/cves/CVE-2026-32146.html - () https://cna.erlef.org/cves/CVE-2026-32146.html - Third Party Advisory
References () https://github.com/gleam-lang/gleam/commit/1aa5d8e594b0aa240bb213fce6ee19c65e6d5bcf - () https://github.com/gleam-lang/gleam/commit/1aa5d8e594b0aa240bb213fce6ee19c65e6d5bcf - Patch
References () https://github.com/gleam-lang/gleam/commit/2dc0467f822c75de94697a912755d172928ee40a - () https://github.com/gleam-lang/gleam/commit/2dc0467f822c75de94697a912755d172928ee40a - Patch
References () https://github.com/gleam-lang/gleam/security/advisories/GHSA-vq5j-55vx-wq8j - () https://github.com/gleam-lang/gleam/security/advisories/GHSA-vq5j-55vx-wq8j - Exploit, Vendor Advisory
References () https://osv.dev/vulnerability/EEF-CVE-2026-32146 - () https://osv.dev/vulnerability/EEF-CVE-2026-32146 - Third Party Advisory
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 7.8
CPE cpe:2.3:a:lpil:gleam:*:*:*:*:*:*:*:*
First Time Lpil
Lpil gleam

14 Apr 2026, 10:16

Type Values Removed Values Added
Summary (en) Improper path validation vulnerability in the Gleam compiler's handling of git dependencies allows arbitrary file system modification during dependency download. Dependency names from gleam.toml and manifest.toml are incorporated into filesystem paths without sufficient validation or confinement to the intended dependency directory, allowing attacker-controlled paths (via relative traversal such as ../ or absolute paths) to target filesystem locations outside that directory. When resolving git dependencies (e.g. via gleam deps download), the computed path is used for filesystem operations including directory deletion and creation. This vulnerability occurs during the dependency resolution and download phase, which is generally expected to be limited to fetching and preparing dependencies within a confined directory. A malicious direct or transitive git dependency can exploit this issue to delete and overwrite arbitrary directories outside the intended dependency directory, including attacker-chosen absolute paths, potentially causing data loss. In some environments, this may be further leveraged to achieve code execution, for example by overwriting git hooks or shell configuration files. This issue affects Gleam from 1.9.0-rc1 until 1.15.3 and 1.16.0-rc1. (en) Improper path validation vulnerability in the Gleam compiler's handling of git dependencies allows arbitrary file system modification during dependency download. Dependency names from gleam.toml and manifest.toml are incorporated into filesystem paths without sufficient validation or confinement to the intended dependency directory, allowing attacker-controlled paths (via relative traversal such as ../ or absolute paths) to target filesystem locations outside that directory. When resolving git dependencies (e.g. via gleam deps download), the computed path is used for filesystem operations including directory deletion and creation. This vulnerability occurs during the dependency resolution and download phase, which is generally expected to be limited to fetching and preparing dependencies within a confined directory. A malicious direct or transitive git dependency can exploit this issue to delete and overwrite arbitrary directories outside the intended dependency directory, including attacker-chosen absolute paths, potentially causing data loss. In some environments, this may be further leveraged to achieve code execution, for example by overwriting git hooks or shell configuration files. This issue affects Gleam from 1.9.0-rc1 until 1.15.4.
References
  • {'url': 'https://github.com/gleam-lang/gleam/commit/55bb36e6d7febfbbc48c4d001e0ae13eb0312d78', 'source': '6b3ad84c-e1a6-4bf7-a703-f496b71e49db'}
  • () https://github.com/gleam-lang/gleam/commit/2dc0467f822c75de94697a912755d172928ee40a -

11 Apr 2026, 14:16

Type Values Removed Values Added
New CVE

Information

Published : 2026-04-11 14:16

Updated : 2026-05-21 20:14


NVD link : CVE-2026-32146

Mitre link : CVE-2026-32146

CVE.ORG link : CVE-2026-32146


JSON object : View

Products Affected

lpil

  • gleam
CWE
CWE-22

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')