CVE-2026-32146: Improper Path Validation in Git Dependency Handling Allows Arbitrary File System Modification
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.
Security readout for executives and security teams
Plain-English summary
A malicious direct or transitive Git dependency can make affected Gleam versions delete or overwrite directories outside the dependency cache during dependency download. This can cause data loss and, in some environments, code execution by replacing sensitive files. Exploitation requires someone or an automated build to process the malicious dependency.
Executive priority
Prioritize remediation for CI runners and developer systems that build third-party or externally contributed Gleam projects. The high potential impact and supply-chain reach justify prompt action, although no active exploitation is established in the supplied evidence. Restrict build permissions immediately where upgrading cannot occur promptly.
Technical view
Gleam incorporates dependency names from gleam.toml and manifest.toml into filesystem paths without adequate validation or confinement. Traversal or absolute paths can escape the intended dependency directory. Subsequent deletion and creation operations may modify attacker-selected locations. The supplied record reports versions from 1.9.0-rc1 until 1.15.4 as affected and assigns CVSS 3.1 score 8.6.
Likely exposure
Exposure is most likely in developer workstations and CI/CD systems using an affected Gleam release to download Git dependencies. Risk increases when projects, manifests, lockfiles, or transitive dependencies come from untrusted or compromised sources, particularly where builds have broad filesystem permissions.
Exploitation context
The supplied sources do not report known active exploitation, and the CVE is not listed as KEV. Exploitation occurs during Git dependency resolution and requires a user or automated process to initiate dependency downloading. Potential impact includes arbitrary directory deletion, file replacement, data loss, credential exposure, and context-dependent code execution.
Researcher notes
This is CWE-22 with scope change and high confidentiality, integrity, and availability impact. The dangerous sink includes directory deletion and creation after attacker-influenced path construction. Assess both direct and transitive Git dependency metadata. The bundle links two patch commits, but does not unambiguously state the first fixed release; confirm exact version boundaries in the vendor advisory.
Mitigation direction
Follow the Gleam advisory and move to a vendor-designated release outside the affected range.
Pause Git dependency downloads for untrusted or newly changed projects until remediation is verified.
Run dependency resolution in isolated, least-privileged environments with narrowly scoped writable storage.
Review direct and transitive Git dependencies, manifests, and lockfile changes before allowing builds.
Maintain recoverable backups for developer and build-system data accessible to Gleam processes.
Validation and detection
Inventory Gleam versions across developer systems, build images, and CI runners.
Identify workflows that execute Git dependency downloads using potentially affected releases.
Inspect dependency names in gleam.toml and manifest.toml for absolute paths or traversal components.
Review recent filesystem deletion or overwrite events associated with Gleam dependency operations.
Confirm remediated builds cannot write outside their designated workspace and dependency directories.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
ADP timelineredhat-SADP
Made public.
Apr 11, 2026, 12:59 UTC (UTC+00:00)
CVE publishedCVE Program
The CVE record was published.
Apr 11, 2026, 12:59 UTC (UTC+00:00)
ADP timelineredhat-SADP
Reported to Red Hat.
Apr 11, 2026, 14:00 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
Sep 8, 2026, 00:58 UTC (UTC+00:00)
ADP provider summaries
CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPgleam: Gleam compiler: Arbitrary file system modification and potential code execution via improper path validation in git dependency handling.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.