LiveActive security incident?Get immediate response
CVE Record

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.

HighCVSS 8.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A malicious Gleam git dependency can cause the compiler to delete or recreate directories outside the intended dependency cache during dependency download. This can lead to data loss and, in some environments, possible code execution by overwriting sensitive local files.

Executive priority

Treat this as a high-priority build-chain risk where Gleam is used with git dependencies. Prioritize CI and developer systems because compromise can destroy files or affect build integrity.

Technical view

Gleam failed to confine dependency names from gleam.toml and manifest.toml when building filesystem paths for git dependency resolution. Traversal or absolute paths could escape the dependency directory, affecting versions from 1.9.0-rc1 until 1.15.4. The issue is classified as CWE-22 with CVSS 8.6.

Likely exposure

Exposure is most likely in developer workstations, CI runners, and build systems that use affected Gleam versions and download direct or transitive git dependencies from untrusted or compromised sources.

Exploitation context

The source bundle does not show known active exploitation, and KEV is false. Exploitation requires user interaction through dependency resolution, but no privileges are required once a vulnerable workflow processes a malicious dependency name.

Researcher notes

Evidence supports arbitrary filesystem modification through insufficient path validation during git dependency handling. Patch references exist, but this bundle does not include exact release remediation wording beyond the affected range and commits.

Mitigation direction

  • Upgrade Gleam according to the vendor advisory and patch references.
  • Review Gleam projects for direct and transitive git dependencies.
  • Avoid untrusted git dependencies in build and CI workflows.
  • Run dependency downloads in isolated, disposable build environments.
  • Check vendor guidance for any additional fixed-version details.

Validation and detection

  • Inventory installed Gleam versions across developer and CI systems.
  • Identify projects with git dependencies in Gleam manifests.
  • Review lockfiles or manifests for unusual dependency names or paths.
  • Check recent build logs for unexpected dependency directory operations.
  • Confirm upgraded environments no longer use affected Gleam releases.
Prepared
Confidence
high
Sources
8

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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

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.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-32146 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

2CVSS vectors
5Timeline events
2ADP providers
9Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: noTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H1.86redhat-SADP
8.3CVSS 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:H/VA:N/SC:H/SI:H/SA:HEEF

Vulnerability scoring details

Base CVSS 4.0 score

8.3High
CVSS 4.0 vector shape for CVE-2026-32146Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

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.
other:Red Hat severity ratingcvssV3_1
  • 2026-04-11T14:00:57.102Z: Reported to Red Hat.
  • 2026-04-11T12:59:22.911Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GleamGleamgleam, 1.9.0-rc1unaffected
GleamGleamgleam-lang/gleam, 1.9.0-rc1, a4fde22445ab8e5cc79c2ff48971616cb570702cunaffected
GleamGleamgleam-lang/gleam, v1.9.0-rc1-elixir, v1.9.0-rc1-erlang, v1.9.0-rc1-node, v1.9.0-rc1-node-slim, v1.9.0-rc1-elixir-slim, v1.9.0-rc1-erlang-slim, v1.9.0-rc1-erlang-alpine, v1.9.0-rc1-elixir-alpine, v1.9.0-rc1-node-alpine, v1.9.0-rc1-scratchunaffected
Weakness

CWE details

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.