CVE-2026-32146Improper Path Validation in Git Dependency Handling Allows Arbitrary File System Modification
- 8.3HighCVSS base score
- 0.26%Exploitation in 30 daysEPSS · top 82% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- YesPublic exploitsa reference or SSVC says so
Description
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 before 1.15.4 and from 1.16.0-rc1 before 1.16.0-rc2.
Public exploit
An exploit or proof of concept is public: anyone can try it against an unpatched system. CISA's SSVC rates its exploitation: a proof of concept is public.
Timeline
ID reserved
By EEF
- 32 days later
· 32 days later
Published
- 7 months later
· 7 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| EEFCNA (assigner) | 4.0 | High8.3 | 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 |
| redhat-SADPADP (enrichment) | 3.1 | High8.6 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
| NVDNVD · Modified | 4.0 | High8.3 | 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 |
- EPSS (exploitation in 30 days)
- 0.26% · top 82% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: poc · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 8.3.
Affected products
- affected 1.9.0-rc1 – < 1.15.4
- affected 1.16.0-rc1 – < 1.16.0-rc2
- affected v1.9.0-rc1-elixir – < v1.15.4-elixir
- affected v1.9.0-rc1-erlang – < v1.15.4-erlang
- affected v1.9.0-rc1-node – < v1.15.4-node
- affected v1.9.0-rc1-node-slim – < v1.15.4-node-slim
- affected v1.9.0-rc1-elixir-slim – < v1.15.4-elixir-slim
- affected v1.9.0-rc1-erlang-slim – < v1.15.4-erlang-slim
- affected v1.9.0-rc1-erlang-alpine – < v1.15.4-erlang-alpine
- affected v1.9.0-rc1-elixir-alpine – < v1.15.4-elixir-alpine
- affected v1.9.0-rc1-node-alpine – < v1.15.4-node-alpine
- affected v1.9.0-rc1-scratch – < v1.15.4-scratch
- affected v1.16.0-rc1-elixir – < v1.16.0-rc2-elixir
- affected v1.16.0-rc1-erlang – < v1.16.0-rc2-erlang
- affected v1.16.0-rc1-node – < v1.16.0-rc2-node
- affected v1.16.0-rc1-node-slim – < v1.16.0-rc2-node-slim
- affected v1.16.0-rc1-elixir-slim – < v1.16.0-rc2-elixir-slim
- affected v1.16.0-rc1-erlang-slim – < v1.16.0-rc2-erlang-slim
- affected v1.16.0-rc1-erlang-alpine – < v1.16.0-rc2-erlang-alpine
- affected v1.16.0-rc1-elixir-alpine – < v1.16.0-rc2-elixir-alpine
- affected v1.16.0-rc1-node-alpine – < v1.16.0-rc2-node-alpine
- affected v1.16.0-rc1-scratch – < v1.16.0-rc2-scratch
- affected a4fde22445ab8e5cc79c2ff48971616cb570702c – < *
What to do
Solution: Upgrade to Gleam 1.15.4 or later. Both patches must be applied: the original incomplete fix (1aa5d8e594b0aa240bb213fce6ee19c65e6d5bcf, backported as 55bb36e6d7febfbbc48c4d001e0ae13eb0312d78 to 1.15) and the follow-up fix (2dc0467f822c75de94697a912755d172928ee40a, backported as 92aae3913570e8d8962f6399404777d313045bfa to 1.15). Gleam 1.15.4 includes both.
Workaround: * Avoid using untrusted git dependencies, especially without pinning to a specific commit SHA * Review dependency trees carefully, including transitive git dependencies * Run dependency resolution commands in a restricted or isolated environment (e.g. containers)
References
References10
- Improper Path Validation in Git Dependency Handling Allows Arbitrary File System Modification (opens in a new tab)vendor-advisoryrelated
- EEF CNA record for CVE-2026-32146 (opens in a new tab)related
- OSV record EEF-CVE-2026-32146 (opens in a new tab)related
- Error immediately for invalid config (opens in a new tab)patch
- Introducing commit a4fde22 in gleam-lang/gleam (opens in a new tab)related
- Fix commit 2dc0467 in gleam-lang/gleam (opens in a new tab)patch
- Fix commit 92aae39 in gleam-lang/gleam (opens in a new tab)patch
- https://access.redhat.com/security/cve/CVE-2026-32146 (opens in a new tab)vdb-entryx_refsource_REDHAT
- RHBZ#2457578 (opens in a new tab)issue-trackingx_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-32146.json (opens in a new tab)x_sadp-csaf-vex
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-21680 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-32146)Record last updated .