Gleam
Monthly
Package integrity bypass in the Gleam build tool (compiler-cli) versions 0.18.0 up to 1.18.0 lets an adversary-in-the-middle substitute forged Hex dependency contents during resolution. Although Gleam fetches signature-verified registry metadata, gleam_cli::dependencies::lookup_package instead recorded the SHA-256 outer_checksum and dependency names from a second, unsigned Hex API call into manifest.toml, so the forged tarball validates against its own forged checksum. Exploitation requires an attacker who can both perform TLS interception with a CA trusted by the Gleam process and modify the tarball; there is no public exploit identified at time of analysis and it is not in CISA KEV.
Path traversal in Gleam compiler versions 1.9.0-rc1 through 1.15.3 and 1.16.0-rc1 allows arbitrary file system modification when resolving git dependencies, enabling attackers to delete and overwrite directories outside the intended dependency folder via malicious dependency names containing relative or absolute paths. A user must invoke dependency download (e.g., gleam deps download) for exploitation; attackers can leverage this to cause data loss or achieve code execution by overwriting git hooks or shell configuration files. Vendor-released patches are available.
Package integrity bypass in the Gleam build tool (compiler-cli) versions 0.18.0 up to 1.18.0 lets an adversary-in-the-middle substitute forged Hex dependency contents during resolution. Although Gleam fetches signature-verified registry metadata, gleam_cli::dependencies::lookup_package instead recorded the SHA-256 outer_checksum and dependency names from a second, unsigned Hex API call into manifest.toml, so the forged tarball validates against its own forged checksum. Exploitation requires an attacker who can both perform TLS interception with a CA trusted by the Gleam process and modify the tarball; there is no public exploit identified at time of analysis and it is not in CISA KEV.
Path traversal in Gleam compiler versions 1.9.0-rc1 through 1.15.3 and 1.16.0-rc1 allows arbitrary file system modification when resolving git dependencies, enabling attackers to delete and overwrite directories outside the intended dependency folder via malicious dependency names containing relative or absolute paths. A user must invoke dependency download (e.g., gleam deps download) for exploitation; attackers can leverage this to cause data loss or achieve code execution by overwriting git hooks or shell configuration files. Vendor-released patches are available.