<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T07:26:43.698164+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-220270</id>
    <title>EUVD-2026-220270</title>
    <updated>2026-10-04T07:26:43.784414+00:00</updated>
    <content>EUVD-2026-220270</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-220270"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-25204</id>
    <title>fkie_cve-2025-25204</title>
    <updated>2026-10-04T07:26:43.784452+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>`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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-25204"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-fgw4-v983-mgp8</id>
    <title>GHSA-fgw4-v983-mgp8 — `gh attestation verify` returns incorrect exit code during verification if no attestations are present</title>
    <updated>2026-10-04T07:26:43.784491+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/cli/cli/v2</p>
<p>### Summary</p>
<p>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 &lt;value&gt;` 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.</p>
<p>Users are advised to update `gh` to version `v2.67.0` as soon as possible.</p>
<p>Initial report: https://github.com/cli/cli/issues/10418
Fix: https://github.com/cli/cli/pull/10421</p>
<p>### Details</p>
<p>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.</p>
<p>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.</p>
<p>### PoC</p>
<p>Run `gh attestation verify` with local attestations using the `--bundle` flag and…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-fgw4-v983-mgp8"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2025-25204</id>
    <title>msrc_CVE-2025-25204 — `gh attestation verify` returns incorrect exit code during verification if no attestations are present</title>
    <updated>2026-10-04T07:26:43.784538+00:00</updated>
    <content>msrc_CVE-2025-25204</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2025-25204"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2025:14889-1</id>
    <title>openSUSE-SU-2025:14889-1 — govulncheck-vulndb-0.0.20250312T181707-1.1 on GA media</title>
    <updated>2026-10-04T07:26:43.784557+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>govulncheck-vulndb-0.0.20250312T181707-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2025:14889-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-25204</id>
    <title>Withdrawn: UBUNTU-CVE-2025-25204</title>
    <updated>2026-10-04T07:26:43.784586+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> Ubuntu:22.04:LTS: gh, Ubuntu:Pro:24.04:LTS: gh, Ubuntu:25.10: gh</p>
<p>`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.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-25204"/>
  </entry>
</feed>
