Most recent entries from all

EUVD-2026-220270

fkie_cve-2025-25204

`gh` is GitHub’s official command line tool. Starting in version 2.49.0 and prior to version 2.67.0, under certain conditions, a bug in GitHub's Artifact Attestation cli tool `gh attestation verify` causes it to return a zero exit status when no attestations are present. This behavior is incorrect: When no attestations are present, `gh attestation verify` should return a non-zero exit status code, thereby signaling verification failure. An attacker can abuse this flaw to, for example, deploy malicious artifacts in any system that uses `gh attestation verify`'s exit codes to gatekeep deployments. Users are advised to update `gh` to patched version `v2.67.0` as soon as possible.

GHSA-fgw4-v983-mgp8 — `gh attestation verify` returns incorrect exit code during verification if no attestations are present

Affected: Go: github.com/cli/cli/v2

### Summary

A bug in GitHub's Artifact Attestation CLI tool, `gh attestation verify`, may return an incorrect zero exit status when no matching attestations are found for the specified `--predicate-type <value>` or the default `https://slsa.dev/provenance/v1` if not specified. This issue only arises if an artifact has an attestation with a predicate type different from the one provided in the command. As a result, users relying solely on these exit codes may mistakenly believe the attestation has been verified, despite the absence of an attestation with the specified predicate type and the tool printing a verification failure.

Users are advised to update `gh` to version `v2.67.0` as soon as possible.

Initial report: https://github.com/cli/cli/issues/10418 Fix: https://github.com/cli/cli/pull/10421

### Details

The gh attestation verify command fetches, loads, and attempts to verify attestations associated with a given artifact for a specified predicate type. If an attestation is found, but the predicate type does not match the one specified in the `gh attestation verify` command, the verification fails, but the program exits early.

Due to a re-used uninitialized error variable, when no matching attestations are found, the relevant function returns `nil` instead of an error, causing the program to exit with a status code of `0`, which incorrectly suggests successful verification.

### PoC

Run `gh attestation verify` with local attestations using the `--bundle` flag and…

msrc_CVE-2025-25204 — `gh attestation verify` returns incorrect exit code during verification if no attestations are present

msrc_CVE-2025-25204

openSUSE-SU-2025:14889-1 — govulncheck-vulndb-0.0.20250312T181707-1.1 on GA media

govulncheck-vulndb-0.0.20250312T181707-1.1 on GA media

Withdrawn: UBUNTU-CVE-2025-25204

Withdrawn by the publisher.

Affected: Ubuntu:22.04:LTS: gh, Ubuntu:Pro:24.04:LTS: gh, Ubuntu:25.10: gh