<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 14:07:10 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: CLEANSTART-2026-EM47790 — Security fixes in tkn 0.42.2-r1</title>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-em47790</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: tkn&lt;/p&gt;
&lt;p&gt;Package tkn version 0.42.2-r1 fixes 57 vulnerabilities: CVE-2025-15558, CVE-2026-34040, CVE-2026-33997, CVE-2025-69725, CVE-2026-34986...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: tkn&lt;/p&gt;
&lt;p&gt;Package tkn version 0.42.2-r1 fixes 57 vulnerabilities: CVE-2025-15558, CVE-2026-34040, CVE-2026-33997, CVE-2025-69725, CVE-2026-34986...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-em47790</guid>
    </item>
    <item>
      <title>EUVD-2026-338588</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-338588</link>
      <description>EUVD-2026-338588</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-338588</guid>
    </item>
    <item>
      <title>fkie_cve-2026-49834</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-49834</link>
      <description>&lt;p&gt;sigstore-go is a Go library for Sigstore signing and verification. Prior to 1.2.0, a verifier configured with WithTransparencyLog(N&amp;gt;1) or WithSignedCertificateTimestamps(N&amp;gt;1) counts verified witnesses per entry or per validation path rather than per log authority, allowing a single compromised transparency log or CT log to satisfy multi-log threshold requirements and defeat the multi-log policy. This issue is fixed in version 1.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;sigstore-go is a Go library for Sigstore signing and verification. Prior to 1.2.0, a verifier configured with WithTransparencyLog(N&amp;gt;1) or WithSignedCertificateTimestamps(N&amp;gt;1) counts verified witnesses per entry or per validation path rather than per log authority, allowing a single compromised transparency log or CT log to satisfy multi-log threshold requirements and defeat the multi-log policy. This issue is fixed in version 1.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-49834</guid>
    </item>
    <item>
      <title>GHSA-9vcr-p3rj-q5q6 — sigstore-go has a multi-log threshold bypass via single compromised log</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9vcr-p3rj-q5q6</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/sigstore/sigstore-go&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_&lt;/p&gt;
&lt;p&gt;A verifier configured with WithTransparencyLog(N&amp;gt;1) or WithSignedCertificateTimestamps(N&amp;gt;1) expected defense-in-depth against the compromise of a single log instance. However, threshold counting counted verified witnesses per-entry or per-validation-path rather than per-log-authority.&lt;/p&gt;
&lt;p&gt;As a result, a single compromised transparency log could forge multiple entries with different indices, and a single compromised CT log could verify multiple times (either across multiple certificate chains or via multiple embedded SCTs), fully satisfying the multi-log threshold requirements and defeating the multi-log policy.&lt;/p&gt;
&lt;p&gt;Note that this does not affect Cosign, as Cosign sets a threshold of 1.&lt;/p&gt;
&lt;p&gt;### Patches
_Has the problem been patched? What versions should users upgrade to?_&lt;/p&gt;
&lt;p&gt;Upgrade to v1.1.5.&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_&lt;/p&gt;
&lt;p&gt;There is no workaround, beyond relying on trusted logs.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/sigstore/sigstore-go&lt;/p&gt;
&lt;p&gt;### Impact
_What kind of vulnerability is it? Who is impacted?_&lt;/p&gt;
&lt;p&gt;A verifier configured with WithTransparencyLog(N&amp;gt;1) or WithSignedCertificateTimestamps(N&amp;gt;1) expected defense-in-depth against the compromise of a single log instance. However, threshold counting counted verified witnesses per-entry or per-validation-path rather than per-log-authority.&lt;/p&gt;
&lt;p&gt;As a result, a single compromised transparency log could forge multiple entries with different indices, and a single compromised CT log could verify multiple times (either across multiple certificate chains or via multiple embedded SCTs), fully satisfying the multi-log threshold requirements and defeating the multi-log policy.&lt;/p&gt;
&lt;p&gt;Note that this does not affect Cosign, as Cosign sets a threshold of 1.&lt;/p&gt;
&lt;p&gt;### Patches
_Has the problem been patched? What versions should users upgrade to?_&lt;/p&gt;
&lt;p&gt;Upgrade to v1.1.5.&lt;/p&gt;
&lt;p&gt;### Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_&lt;/p&gt;
&lt;p&gt;There is no workaround, beyond relying on trusted logs.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9vcr-p3rj-q5q6</guid>
    </item>
    <item>
      <title>RHSA-2026:44162 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:44162</link>
      <description>&lt;p&gt;github.com/sigstore/sigstore-go: sigstore-go: Security Policy Bypass via Compromised Log github.com/sigstore/sigstore-go: sigstore-go: Signature bypass allows acceptance of bundles signed with expired keys golang.org/x/text: golang.org/x/text: Denial of Service via invalid UTF-8 input&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;github.com/sigstore/sigstore-go: sigstore-go: Security Policy Bypass via Compromised Log github.com/sigstore/sigstore-go: sigstore-go: Signature bypass allows acceptance of bundles signed with expired keys golang.org/x/text: golang.org/x/text: Denial of Service via invalid UTF-8 input&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:44162</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-49834</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-49834</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:26.04:LTS: sigstore-go&lt;/p&gt;
&lt;p&gt;sigstore-go is a Go library for Sigstore signing and verification. Prior to 1.2.0, a verifier configured with WithTransparencyLog(N&amp;gt;1) or WithSignedCertificateTimestamps(N&amp;gt;1) counts verified witnesses per entry or per validation path rather than per log authority, allowing a single compromised transparency log or CT log to satisfy multi-log threshold requirements and defeat the multi-log policy. This issue is fixed in version 1.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:26.04:LTS: sigstore-go&lt;/p&gt;
&lt;p&gt;sigstore-go is a Go library for Sigstore signing and verification. Prior to 1.2.0, a verifier configured with WithTransparencyLog(N&amp;gt;1) or WithSignedCertificateTimestamps(N&amp;gt;1) counts verified witnesses per entry or per validation path rather than per log authority, allowing a single compromised transparency log or CT log to satisfy multi-log threshold requirements and defeat the multi-log policy. This issue is fixed in version 1.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-49834</guid>
    </item>
  </channel>
</rss>
