boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Thursday, November 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2026-32146

Gleam Gleam — Improper Path Validation in Git Dependency Handling Allows Arbitrary File System Modification
  AV  AC  AT  PR  UI  VC  VI  VA   CVSS    EPSS   %ile   KEV
   L   L   N   N   A   N   H   N    8.3   .0026   18.6     —
AFFECTED
  Product  Versions                                    Fixed
  Gleam    1.9.0-rc1 –                                 —
  Gleam    v1.9.0-rc1-elixir –                         —
  Gleam    a4fde22445ab8e5cc79c2ff48971616cb570702c –  2dc0467f822c75de94697a912755d172928ee40a
TIMELINE
  Mar 10  Reserved by EEF
  Apr 11  Published (CNA: EEF)
  Sep 8   EXPLOIT PUBLISHED — CVE-2026-32146 (Gleam). Public exploit reference added.
  Nov 10  EXPLOIT PUBLISHED — CVE-2026-32146 (Gleam). Public exploit reference added.
CWE-22 · CNA: EEF · CVSS v4.0 · 10 references · NVD status: Modified

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.

Lifecycle

Complete event history — 4 events, chronological
DateEventDetail
March 10, 2026ReservedReserved by EEF
April 11, 2026PublishedPublished (CNA: EEF)
September 8, 2026EXPLOIT PUBLISHEDEXPLOIT PUBLISHED — CVE-2026-32146 (Gleam). Public exploit reference added.
November 10, 2026EXPLOIT PUBLISHEDEXPLOIT PUBLISHED — CVE-2026-32146 (Gleam). Public exploit reference added.

Affected

Affected products and packages — 3 rows
VendorProduct / PackageEcosystemVersion introducedFixed
GleamGleam—1.9.0-rc1—
GleamGleam—v1.9.0-rc1-elixir—
GleamGleam—a4fde22445ab8e5cc79c2ff48971616cb570702c2dc0467f822c75de94697a912755d172928ee40a

Weaknesses

CWE-22

References (10)

Related

Authoritative record: CVE-2026-32146 at cve.org

Vendors: gleam

Weaknesses: CWE-22

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-32146 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Thursday, November 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.