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-59247Insufficient verification of Hex package metadata in Gleam

Description

Insufficient Verification of Data Authenticity vulnerability in Gleam allows an adversary in the middle to substitute forged Hex package contents during dependency resolution. During dependency resolution Gleam fetches package metadata from the signature-verified Hex repository, which covers each release's dependency requirements and SHA-256 outer_checksum. After resolving versions, gleam_cli::dependencies::lookup_package makes a second request to the unsigned Hex API through gleam_core::hex::get_package_release and records the outer_checksum and dependency names from that JSON response into manifest.toml, instead of the values from the verified repository metadata. The Hex repository signature does not cover the API response. An adversary in the middle who can intercept TLS with a certificate trusted by the Gleam process (for example a TLS-inspecting proxy using a CA in the operating system trust store or added through GLEAM_CACERTS_PATH), and who can modify both the API release response and the corresponding repository tarball, can supply a package archive with a matching forged checksum without the Hex repository signing key. Gleam verifies the forged tarball against the forged checksum, accepts it, and extracts it as a dependency source, resulting in loss of integrity of the downloaded package contents. Only projects that resolve or update Hex dependencies are affected, which happens when the manifest is missing, a dependency is added or updated, or dependency requirements change. Builds that reuse an unchanged, known-good manifest.toml continue to verify tarballs against its pinned checksum. This issue affects gleam: from 0.18.0-rc1 before 1.18.0.

Timeline

  1. ID reserved

    By EEF

  2. · 25 days later

    Published

  3. · 3 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-59247, by who scored it
Scored byCVSSScoreVector
EEFCNA (assigner)4.0High7.6CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
NVDNVD · Deferred4.0High7.6CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/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 91% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Gleam · Gleam

    • affected 0.18.0-rc1 – < 1.18.0
  • Gleam · Gleam

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

    • affected 8447b78cc844ff4aec44eea23dbd68d1fea11f11 – < c9c0d48c123c8abae6db8dd61b25ccb427ed3d35

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .