<?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://db.gcve.eu</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>Tue, 03 Nov 2026 12:45:31 +0000</lastBuildDate>
    <item>
      <title>GHSA-fphv-w9fq-2525 — go-tuf improperly validates the configured threshold for delegations</title>
      <link>https://db.gcve.eu/vuln/ghsa-fphv-w9fq-2525</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/theupdateframework/go-tuf/v2&lt;/p&gt;
&lt;p&gt;# Security Disclosure: Improper validation of configured threshold for delegations&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;A compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Unathorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Upgrade to v2.3.1&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Always make sure that the TUF metadata roles are configured with a threshold of at least 1.&lt;/p&gt;
&lt;p&gt;## Affected code:&lt;/p&gt;
&lt;p&gt;The `metadata.VerifyDelegate` did not verify the configured threshold prior to comparison. This means that a misconfigured TUF repository could disable the signature verification by setting the threshold to 0, or a negative value (and so always make the signature threshold computation to pass).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/theupdateframework/go-tuf/v2&lt;/p&gt;
&lt;p&gt;# Security Disclosure: Improper validation of configured threshold for delegations&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;A compromised or misconfigured TUF repository can have the configured value of signature thresholds set to 0, which effectively disables signature verification.&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Unathorized modification to TUF metadata files is possible at rest, or during transit as no integrity checks are made.&lt;/p&gt;
&lt;p&gt;## Patches&lt;/p&gt;
&lt;p&gt;Upgrade to v2.3.1&lt;/p&gt;
&lt;p&gt;## Workarounds&lt;/p&gt;
&lt;p&gt;Always make sure that the TUF metadata roles are configured with a threshold of at least 1.&lt;/p&gt;
&lt;p&gt;## Affected code:&lt;/p&gt;
&lt;p&gt;The `metadata.VerifyDelegate` did not verify the configured threshold prior to comparison. This means that a misconfigured TUF repository could disable the signature verification by setting the threshold to 0, or a negative value (and so always make the signature threshold computation to pass).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-fphv-w9fq-2525</guid>
    </item>
  </channel>
</rss>
