NVD / CVE Program· CNA EEF

CVE-2026-32146: Improper Path Validation in Git Dependency Handling Allows Arbitrary File System Modification

Noroxi assessment

Priority: Monitor (action score 33/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
Someone with local access to the system can trigger it. No account or password is required. No special conditions are required; it is repeatable.
Fixed version: Gleam Gleam 1.15.4, 2dc0467f822c75de94697a912755d172928ee40a, 92aae3913570e8d8962f6399404777d313045bfa.

Low priority for now. Upgrade to Gleam Gleam 1.15.4, 2dc0467f822c75de94697a912755d172928ee40a, 92aae3913570e8d8962f6399404777d313045bfa or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.3 · v4.0—No exploit Fix available

Path traversal

Published: Apr 11, 2026
Updated: Sep 8, 2026
EPSS: 0.2% · 15th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 33 / 40 · 8.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: proof of concept
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · EEF: 8.3; NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
lpil	gleam	cpe:2.3:a:lpil:gleam

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

lpil gleam1.9.0 and later · before 1.15.4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (EEF). Independent of NVD's CPE analysis and usually ahead of it.

Gleam Gleam
- 1.9.0-rc1 and lateraffected · semverfixed in 1.15.4
- 1.9.0-rc1 and lateraffected · semverfixed in 1.15.4
- a4fde22445ab8e5cc79c2ff48971616cb570702c and lateraffected · gitfixed in 92aae3913570e8d8962f6399404777d313045bfa, 2dc0467f822c75de94697a912755d172928ee40a
- v1.9.0-rc1-elixir and later · before v1.15.4-elixiraffected · other
- v1.9.0-rc1-erlang and later · before v1.15.4-erlangaffected · other
- v1.9.0-rc1-node and later · before v1.15.4-nodeaffected · other
- v1.9.0-rc1-node-slim and later · before v1.15.4-node-slimaffected · other
- v1.9.0-rc1-elixir-slim and later · before v1.15.4-elixir-slimaffected · other
- v1.9.0-rc1-erlang-slim and later · before v1.15.4-erlang-slimaffected · other
- v1.9.0-rc1-erlang-alpine and later · before v1.15.4-erlang-alpineaffected · other

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Gleam Gleam	1.15.4	Vendor (CNA)
Gleam Gleam	2dc0467f822c75de94697a912755d172928ee40a	Vendor (CNA)
Gleam Gleam	92aae3913570e8d8962f6399404777d313045bfa	Vendor (CNA)
Gleam Gleam	v1.15.4-elixir	Vendor (CNA)
Gleam Gleam	v1.15.4-elixir-alpine	Vendor (CNA)
Gleam Gleam	v1.15.4-elixir-slim	Vendor (CNA)
Gleam Gleam	v1.15.4-erlang	Vendor (CNA)
Gleam Gleam	v1.15.4-erlang-alpine	Vendor (CNA)
Gleam Gleam	v1.15.4-erlang-slim	Vendor (CNA)
Gleam Gleam	v1.15.4-node	Vendor (CNA)
Gleam Gleam	v1.15.4-node-alpine	Vendor (CNA)
Gleam Gleam	v1.15.4-node-slim	Vendor (CNA)
Gleam Gleam	v1.15.4-scratch	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

John Downeyremediation developer
Louis Pilfoldanalyst
Jonatan Männchen / EEFanalyst

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Someone with local access to the system can trigger it.
No account or password is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Local
Attack complexity: Low
Privileges required: None
User interaction: A
Scope: X

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS 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

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:11 PM UTC

For records you follow, these changes also arrive as notifications. →

References

cna.erlef.org/cves/CVE-2026-32146.html

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records