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

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

Published: 2025-02-14 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-25204 is rated Low Risk (39.7/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.19%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-25204

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-25 0.11% 0.19% +0.09%
2 2025-11-21 0.17% 0.11% -0.07%
3 2025-11-18 — 0.17% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-25204

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.8 4.0 [email protected]

Weakness enumeration for CVE-2025-25204

GitHub Security Advisory for CVE-2025-25204

GHSA-fgw4-v983-mgp8 · Severity: medium · Ecosystem: go — `gh attestation verify` returns incorrect exit code during verification if no attestations are present

OS Trackers for CVE-2025-25204

vendor priority summary link
debian unimportant CVE-2025-25204 unimportant priority: Debian including 1 source packages (gh), 3 status rows across 3 suites (bookworm, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2025-25204
ubuntu medium CVE-2025-25204 medium priority: Ubuntu including 1 source packages (gh), 7 status rows across 7 suites (focal, jammy, noble, oracular, plucky, questing, upstream): not-affected 3, ignored 2, DNE 1, released 1. https://ubuntu.com/security/CVE-2025-25204

Affected software / configurations for CVE-2025-25204

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-25204

cvelogic Threat Intelligence