Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-42795Symlink Following in Hex Package Export Allows Embedding Files Outside Project Root

Description

Symlink following vulnerability in Gleam's Hex package export allows files outside the project root to be embedded in the generated package tarball. The file collection helpers (gleam_files, native_files, private_files) in compiler-cli/src/fs.rs use follow_links(true) when walking publishable directories such as src/ and priv/. The collected paths are added to the package archive via add_path_to_tar in compiler-cli/src/publish.rs without verifying that the resolved target remains within the project root. A symlink placed under a publishable directory will cause gleam export hex-tarball or gleam publish to embed the contents of the symlink target into the generated Hex package. An attacker with write access to the project repository can place a symlink in src/ or priv/ pointing to an arbitrary file. When a maintainer or CI pipeline runs gleam publish or gleam export hex-tarball, local files readable by the publisher (such as secrets, tokens, or SSH keys) are silently embedded into the published package artifact. This issue affects gleam: from 0.10.0-rc1 before 1.17.0.

Public exploit

An exploit or proof of concept is public: anyone can try it against an unpatched system. A reference of the record is tagged as an exploit. CISA's SSVC rates its exploitation: a proof of concept is public.

Show the exploits1

Timeline

  1. ID reserved

    By EEF

  2. · 34 days later

    Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-42795, by who scored it
Scored byCVSSScoreVector
EEFCNA (assigner)4.0Medium5.1CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
NVDNVD · Deferred4.0Medium5.1CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/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
EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: poc · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.1.

Affected products

  • Gleam · Gleam

    • affected 0.10.0-rc1 – < 1.17.0
  • Gleam · Gleam

    • affected v0.10.0-rc1-elixir – < v1.17.0-elixir
    • affected v0.10.0-rc1-erlang – < v1.17.0-erlang
    • affected v0.10.0-rc1-node – < v1.17.0-node
    • affected v0.10.0-rc1-node-slim – < v1.17.0-node-slim
    • affected v0.10.0-rc1-elixir-slim – < v1.17.0-elixir-slim
    • affected v0.10.0-rc1-erlang-slim – < v1.17.0-erlang-slim
    • affected v0.10.0-rc1-erlang-alpine – < v1.17.0-erlang-alpine
    • affected v0.10.0-rc1-elixir-alpine – < v1.17.0-elixir-alpine
    • affected v0.10.0-rc1-node-alpine – < v1.17.0-node-alpine
    • affected v0.10.0-rc1-scratch – < v1.17.0-scratch
  • Gleam · Gleam

    • affected c82a2d83bd0c06cafdc196820deb3f89a9b3ff7c – < 6435a5528b9ae0449e2f32be579641ec485f6866

What to do

Workaround: * Avoid running gleam publish or gleam export hex-tarball on untrusted projects * Review the contents of src/ and priv/ for unexpected symlinks before publishing * Run publishing commands in a restricted or isolated environment (e.g. containers)

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-42795 badge
[![CVE-2026-42795](https://cveledger.app/badge/CVE-2026-42795.svg)](https://cveledger.app/cve/CVE-2026-42795)

Record last updated .