Skip to content
Noroxi
NVD / CVE Program· CNA EEF

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

Noroxi assessment

Priority: Monitor (action score 20/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.19% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
  • Fixed version: Gleam Gleam 1.17.0, 6435a5528b9ae0449e2f32be579641ec485f6866, v1.17.0-elixir.

Low priority for now. Upgrade to Gleam Gleam 1.17.0, 6435a5528b9ae0449e2f32be579641ec485f6866, v1.17.0-elixir 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

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 until 1.17.0.

MediumCVSS 5.1 · v4.0—No exploit Fix available
Published
Jun 2, 2026
Updated
Oct 6, 2026
EPSS
0.1% · 9th percentile

Report tools

JSON

Action score

20

Monitor

Low priority for now.

CVSS
20 / 40 · 5.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

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
5.1
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

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.

Follow CVE-2026-42795

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for gleam records

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.

—

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

    • 0.10.0-rc1 and later · before 1.17.0affected · semver
    • 0.10.0-rc1 and later · before 1.17.0affected · semver
    • c82a2d83bd0c06cafdc196820deb3f89a9b3ff7c and later · before 6435a5528b9ae0449e2f32be579641ec485f6866affected · git
    • v0.10.0-rc1-elixir and later · before v1.17.0-elixiraffected · other
    • v0.10.0-rc1-erlang and later · before v1.17.0-erlangaffected · other
    • v0.10.0-rc1-node and later · before v1.17.0-nodeaffected · other
    • v0.10.0-rc1-node-slim and later · before v1.17.0-node-slimaffected · other
    • v0.10.0-rc1-elixir-slim and later · before v1.17.0-elixir-slimaffected · other
    • v0.10.0-rc1-erlang-slim and later · before v1.17.0-erlang-slimaffected · other
    • v0.10.0-rc1-erlang-alpine and later · before v1.17.0-erlang-alpineaffected · other

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
openSUSE:Leap 16.0gleambefore 1.17.0-bp160.1.11.17.0-bp160.1.1
openSUSE:Tumbleweedgleambefore 1.17.0-1.11.17.0-1.1

Same product

gleam: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-103061Path traversal in Gleam via unvalidated package application names
    23Monitor
  • CVE-2026-43965Path Traversal in build/packages/packages.toml Allows Arbitrary Directory Deletion
    22Monitor
  • CVE-2026-32685Path Traversal in gleam docs build via documentation.pages Allows Arbitrary File Read and Write
    18Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
Gleam Gleam1.17.0Vendor (CNA)
Gleam Gleam6435a5528b9ae0449e2f32be579641ec485f6866Vendor (CNA)
Gleam Gleamv1.17.0-elixirVendor (CNA)
Gleam Gleamv1.17.0-elixir-alpineVendor (CNA)
Gleam Gleamv1.17.0-elixir-slimVendor (CNA)
Gleam Gleamv1.17.0-erlangVendor (CNA)
Gleam Gleamv1.17.0-erlang-alpineVendor (CNA)
Gleam Gleamv1.17.0-erlang-slimVendor (CNA)
Gleam Gleamv1.17.0-nodeVendor (CNA)
Gleam Gleamv1.17.0-node-alpineVendor (CNA)
Gleam Gleamv1.17.0-node-slimVendor (CNA)
Gleam Gleamv1.17.0-scratchVendor (CNA)
opensuse:gleam1.17.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)

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.

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.
  • A low-privileged account is enough.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
A
Scope
X

Weakness class (CWE)

CWE-59 · Improper Link Resolution Before File Access ('Link Following')

CVSS vector

CVSS: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

nvd-secondary

Attack context

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

Change log

  1. Fix✗ → ✓

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

References

Show all references (3 more)

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

All records