Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

`gh attestation verify` returns incorrect exit code during verification if no attestations are present

CVSS 3.1 6.3 MEDIUMEUVD CVSS 3.1 6.3 CVSS 3.1 · [email protected] · Secondary 6.3 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/cli/cli/v2 2.67.0osv · severity unknownFixed by github.com/cli/cli/v2 2.67.0KEV status unknown

cve-program · CVE-2025-25204

Published

`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.

Read the publisher's advisory

euvd · EUVD-2025-4090

Published

`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.

Read the publisher's advisory

nvd · CVE-2025-25204

Published

`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.

Read the publisher's advisory

osv · GHSA-fgw4-v983-mgp8

Published

### 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 specify a predicate type with `--predicate-type` that you know will not match any of the attestations the command will attempt to verify. Confirm that the command exits with a zero status code. ### Impact Users who rely exclusively on the exit status code of `gh attestation verify` may incorrectly verify an attestation when the attestation's predicate type does not match the specified predicate type in the command.

Read the publisher's advisory

osv · GO-2025-3467

Published

`gh attestation verify` returns incorrect exit code during verification if no attestations are present in github.com/cli/cli

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2025-25204

Published

cli

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "cli",
                    "product": "cli",
                    "versions": [
                        {
                            "version": ">= 2.49.0, < 2.67.0",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2025-4090

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Feb 14, 2025, 4:38:29 PM

dateUpdated: Mar 3, 2025, 7:13:28 PM

2 related source bulletins · separate from aliases

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

CVE-2025-25204

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

CVE-2024-57603 · CVE-2024-57604 · CVE-2025-0426 · CVE-2025-1243 · CVE-2025-1293 · CVE-2025-1412 · CVE-2025-20051 · CVE-2025-22870 · CVE-2025-22952 · CVE-2025-23387 · CVE-2025-23388 · CVE-2025-23389 · CVE-2025-24016 · CVE-2025-24526 · CVE-2025-24806 · CVE-2025-24976 · CVE-2025-25196 · CVE-2025-25199 · CVE-2025-25204 · CVE-2025-25279 · CVE-2025-25294 · CVE-2025-27088 · CVE-2025-27090 · CVE-2025-27100 · CVE-2025-27112 · CVE-2025-27144 · CVE-2025-27155 · CVE-2025-27414 · CVE-2025-27421 · CVE-2025-27507 · CVE-2025-27509

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2025-25204

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Deferred

Weakness classifications: CWE-390

Original publisher date fields

published: 2025-02-14T17:15:19.140

lastModified: 2026-06-17T09:00:28.767

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-fgw4-v983-mgp8

Published

github.com/cli/cli/v2

Go

SEMVER · introduced 2.49.0 → fixed 2.67.0

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2025-3467

Published

github.com/cli/cli

Go

SEMVER · introduced 0

github.com/cli/cli/v2

Go

SEMVER · introduced 2.49.0 → fixed 2.67.0

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 13:53 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current