<?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-04T08:32:02.749424+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/bit-cosign-2026-39395</id>
    <title>BIT-cosign-2026-39395 — Cosign's verify-blob-attestation reports false positive when payload parsing fails</title>
    <updated>2026-10-04T08:32:02.756575+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: cosign</p>
<p>Cosign provides code signing and transparency for containers and binaries. Prior to 3.0.6 and 2.6.3, cosign verify-blob-attestation may erroneously report a "Verified OK" result for attestations with malformed payloads or mismatched predicate types. For old-format bundles and detached signatures, this was due to a logic flaw in the error handling of the predicate type validation. For new-format bundles, the predicate type validation was bypassed completely. This vulnerability is fixed in 3.0.6 and 2.6.3.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bit-cosign-2026-39395"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-jx39152</id>
    <title>Withdrawn: CLEANSTART-2026-JX39152 — Security fixes in spire-server 1.14.7-r0</title>
    <updated>2026-10-04T08:32:02.756635+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> CleanStart: spire-server</p>
<p>Package spire-server version 1.14.7-r0 fixes 16 vulnerabilities: CVE-2026-49834, CVE-2026-24122, CVE-2026-39395, CVE-2026-41178, CVE-2026-41568...</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-jx39152"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-281260</id>
    <title>EUVD-2026-281260</title>
    <updated>2026-10-04T08:32:02.756659+00:00</updated>
    <content>EUVD-2026-281260</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-281260"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-39395</id>
    <title>fkie_cve-2026-39395</title>
    <updated>2026-10-04T08:32:02.756673+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Cosign provides code signing and transparency for containers and binaries. Prior to 3.0.6 and 2.6.3, cosign verify-blob-attestation may erroneously report a "Verified OK" result for attestations with malformed payloads or mismatched predicate types. For old-format bundles and detached signatures, this was due to a logic flaw in the error handling of the predicate type validation. For new-format bundles, the predicate type validation was bypassed completely. This vulnerability is fixed in 3.0.6 and 2.6.3.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-39395"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-w6c6-c85g-mmv6</id>
    <title>GHSA-w6c6-c85g-mmv6 — Cosign's verify-blob-attestation reports false positive when payload parsing fails</title>
    <updated>2026-10-04T08:32:02.756697+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/sigstore/cosign</p>
<p>## Description</p>
<p>`cosign verify-blob-attestation` may erroneously report a "Verified OK" result for attestations with malformed payloads or mismatched predicate types. For old-format bundles and detached signatures, this was due to a logic flaw in the error handling of the predicate type validation. For new-format bundles, the predicate type validation was bypassed completely.</p>
<p>## Impact</p>
<p>When `cosign verify-blob-attestation` is used without `--check-claims` set to `true`, an attestation that has a valid signature but a malformed or unparsable payload would be incorrectly validated. Additionally, systems relying on `--type &lt;predicate type&gt;` to reject attestations with mismatched types would be lead to trust the unexpected attestation type.</p>
<p>## Patches</p>
<p>v3.0.6, v2.6.3</p>
<p>## Workarounds</p>
<p>Always set `--check-claims=true` for attestation verification.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-w6c6-c85g-mmv6"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10753-1</id>
    <title>openSUSE-SU-2026:10753-1 — cosign-3.0.6-1.1 on GA media</title>
    <updated>2026-10-04T08:32:02.756727+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>cosign-3.0.6-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:10753-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2026:22344-1</id>
    <title>SUSE-SU-2026:22344-1 — Security update for cosign</title>
    <updated>2026-10-04T08:32:02.756743+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for cosign</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2026:22344-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-39395</id>
    <title>UBUNTU-CVE-2026-39395</title>
    <updated>2026-10-04T08:32:02.756756+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:25.10: cosign, Ubuntu:Pro:26.04:LTS: cosign</p>
<p>Cosign provides code signing and transparency for containers and binaries. Prior to 3.0.6 and 2.6.3, cosign verify-blob-attestation may erroneously report a "Verified OK" result for attestations with malformed payloads or mismatched predicate types. For old-format bundles and detached signatures, this was due to a logic flaw in the error handling of the predicate type validation. For new-format bundles, the predicate type validation was bypassed completely. This vulnerability is fixed in 3.0.6 and 2.6.3.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-39395"/>
  </entry>
</feed>
