CVE-2026-32146
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine without logging in, but needs a user to act. High risk of data tampering.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 8.3 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Weakness
- CWE-22 · Path traversal
- Record status
- Modified
Affected
- Lpil Gleam < 1.15.4
Attack profile CVSS 4.0 · 8.3
- Attack vector
- Local
- Complexity
- Low
- Attack requirements
- None
- Privileges needed
- None
- User interaction
- Active
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:H/SI:H/SA:H/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
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-32146.md and follow it. Check whether this project is affected by CVE-2026-32146. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/gleam-lang/gleam/commit/1aa5d8e594b0aa240bb213fce6ee19c65e6d5bcf
- https://github.com/gleam-lang/gleam/commit/2dc0467f822c75de94697a912755d172928ee40a
- https://github.com/gleam-lang/gleam/security/advisories/GHSA-vq5j-55vx-wq8j
References
- https://cna.erlef.org/cves/CVE-2026-32146.html
- https://github.com/gleam-lang/gleam/commit/1aa5d8e594b0aa240bb213fce6ee19c65e6d5bcf
- https://github.com/gleam-lang/gleam/commit/2dc0467f822c75de94697a912755d172928ee40a
- https://github.com/gleam-lang/gleam/security/advisories/GHSA-vq5j-55vx-wq8j
- https://osv.dev/vulnerability/EEF-CVE-2026-32146
- https://access.redhat.com/security/cve/CVE-2026-32146
- https://bugzilla.redhat.com/show_bug.cgi?id=2457578
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-32146.json