Skip to content
Fencer Vulns
medium 6.3

CVE-2025-25204 json

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

published 2025-02-14 20 mo ago modified 2026-09-10 1 mo ago also EUVD-2025-4090 , GHSA-fgw4-v983-mgp8 , GO-2025-3467

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 35%
public exploits
0
none known

Summary

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

Patch / fix

  • go github.com/cli/cli/v2 2.67.0
  • github cli 2.67.0
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250312T181707-1.1

opensuse advisories openSUSE-SU-2025:14889-1

  • gh Azure Linux 3.0 2.62.0-6

azure linux advisories AZL-56885

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-25204 updated cvss 6.3

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

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
20 mo ago

Exploit prediction

0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N
GitHub 3.1 6.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/cli/cli/v2
>=2.49.0, <2.67.0
2.67.0
go github.com/cli/cli
all versions
 no fix listed

Affected products

  • cli cli

Classification

Weakness
  • CWE-390 Detection of Error Condition Without Action

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.