Skip to content
Threat Brief

← All advisories

CVE-2026-59247

High 7.6No known exploitationFix available

Insufficient verification of Hex package metadata in Gleam

Record last updated

CVSS score

7.6

High on a 0 to 10 scale

EPSS, chance of exploitation in 30 days

0.2%

Higher than 9% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

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.

Weakness: CWE-345

Patching and mitigation

Patch status
Fix available (source: CVE record (EEF))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
github.com (opens in a new tab)

Affected products

VendorProductAffected versionsFixed inPer
GleamGleamfrom 0.18.0-rc1 before 1.18.01.18.0CVE Program
GleamGleamfrom 8447b78cc844ff4aec44eea23dbd68d1fea11f11 before c9c0d48c123c8abae6db8dd61b25ccb427ed3d35c9c0d48c123c8abae6db8dd61b25ccb427ed3d35CVE Program
GleamGleamfrom v0.18.0-rc1-elixir before v1.18.0-elixirv1.18.0-elixirCVE Program
GleamGleamfrom v0.18.0-rc1-elixir-alpine before v1.18.0-elixir-alpinev1.18.0-elixir-alpineCVE Program
GleamGleamfrom v0.18.0-rc1-elixir-slim before v1.18.0-elixir-slimv1.18.0-elixir-slimCVE Program
GleamGleamfrom v0.18.0-rc1-erlang before v1.18.0-erlangv1.18.0-erlangCVE Program
GleamGleamfrom v0.18.0-rc1-erlang-alpine before v1.18.0-erlang-alpinev1.18.0-erlang-alpineCVE Program
GleamGleamfrom v0.18.0-rc1-erlang-slim before v1.18.0-erlang-slimv1.18.0-erlang-slimCVE Program
GleamGleamfrom v0.18.0-rc1-node before v1.18.0-nodev1.18.0-nodeCVE Program
GleamGleamfrom v0.18.0-rc1-node-alpine before v1.18.0-node-alpinev1.18.0-node-alpineCVE Program
GleamGleamfrom v0.18.0-rc1-node-slim before v1.18.0-node-slimv1.18.0-node-slimCVE Program
GleamGleamfrom v0.18.0-rc1-scratch before v1.18.0-scratchv1.18.0-scratchCVE Program

Timeline

  1. Disclosure

    CVE record published by EEF

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (EEF)

    Source: CVE record (EEF) (opens in a new tab)

Vendor guidance and references