<?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 01:54:58 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-203345</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-203345</link>
      <description>EUVD-2026-203345</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-203345</guid>
    </item>
    <item>
      <title>fkie_cve-2024-47534</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-47534</link>
      <description>&lt;p&gt;go-tuf is a Go implementation of The Update Framework (TUF). The go-tuf client inconsistently traces the delegations. For example, if targets delegate to &amp;#34;A&amp;#34;, and to &amp;#34;B&amp;#34;, and &amp;#34;B&amp;#34; delegates to &amp;#34;C&amp;#34;, then the client should trace the delegations in the order &amp;#34;A&amp;#34; then &amp;#34;B&amp;#34; then &amp;#34;C&amp;#34; but it may incorrectly trace the delegations &amp;#34;B&amp;#34;-&amp;gt;&amp;#34;C&amp;#34;-&amp;gt;&amp;#34;A&amp;#34;. This vulnerability is fixed in 2.0.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;go-tuf is a Go implementation of The Update Framework (TUF). The go-tuf client inconsistently traces the delegations. For example, if targets delegate to &amp;#34;A&amp;#34;, and to &amp;#34;B&amp;#34;, and &amp;#34;B&amp;#34; delegates to &amp;#34;C&amp;#34;, then the client should trace the delegations in the order &amp;#34;A&amp;#34; then &amp;#34;B&amp;#34; then &amp;#34;C&amp;#34; but it may incorrectly trace the delegations &amp;#34;B&amp;#34;-&amp;gt;&amp;#34;C&amp;#34;-&amp;gt;&amp;#34;A&amp;#34;. This vulnerability is fixed in 2.0.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-47534</guid>
    </item>
    <item>
      <title>GHSA-4f8r-qqr9-fq8j — Incorrect delegation lookups can make go-tuf download the wrong artifact</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4f8r-qqr9-fq8j</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;During the ongoing work on the TUF conformance test suite, we have come across a test that reveals what we believe is a bug in go-tuf with security implications. The bug exists in go-tuf delegation tracing and could result in downloading the wrong artifact.&lt;/p&gt;
&lt;p&gt;We have come across this issue in the test in this PR: https://github.com/theupdateframework/tuf-conformance/pull/115.&lt;/p&gt;
&lt;p&gt;The test - `test_graph_traversal` - sets up a repository with a series of delegations, invokes the clients `refresh()` and then checks the order in which the client traced the delegations. The test shows that the go-tuf client inconsistently traces the delegations in a wrong way. For example, [during one CI run](https://github.com/theupdateframework/tuf-conformance/pull/115#issuecomment-2275625542), the `two-level-delegations` test case triggered a wrong order. The delegations in this look as such:&lt;/p&gt;
&lt;p&gt;```python
&amp;#34;two-level-delegations&amp;#34;: DelegationsTestCase(
        delegations=[
            DelegationTester(&amp;#34;targets&amp;#34;, &amp;#34;A&amp;#34;),
            DelegationTester(&amp;#34;targets&amp;#34;, &amp;#34;B&amp;#34;),
            DelegationTester(&amp;#34;B&amp;#34;, &amp;#34;C&amp;#34;),
        ],
        visited_order=[&amp;#34;A&amp;#34;, &amp;#34;B&amp;#34;, &amp;#34;C&amp;#34;],
    ),
```&lt;/p&gt;
&lt;p&gt;Here, `targets` delegate to `&amp;#34;A&amp;#34;`, and to `&amp;#34;B&amp;#34;`, and `&amp;#34;B&amp;#34;` delegates to `&amp;#34;C&amp;#34;`. The client should trace the delegations in the order `&amp;#34;A&amp;#34;` then `&amp;#34;B&amp;#34;` then `&amp;#34;C&amp;#34;` but in this particular CI run, go-tuf traced the delegations `&amp;#34;B&amp;#34;-&amp;gt;&amp;#34;C&amp;#34;-&amp;gt;&amp;#34;A&amp;#34;`.&lt;/p&gt;
&lt;p&gt;In a subsequent CI run, this test case did not fail, but [another one did](https://github.com/theupdate…&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;During the ongoing work on the TUF conformance test suite, we have come across a test that reveals what we believe is a bug in go-tuf with security implications. The bug exists in go-tuf delegation tracing and could result in downloading the wrong artifact.&lt;/p&gt;
&lt;p&gt;We have come across this issue in the test in this PR: https://github.com/theupdateframework/tuf-conformance/pull/115.&lt;/p&gt;
&lt;p&gt;The test - `test_graph_traversal` - sets up a repository with a series of delegations, invokes the clients `refresh()` and then checks the order in which the client traced the delegations. The test shows that the go-tuf client inconsistently traces the delegations in a wrong way. For example, [during one CI run](https://github.com/theupdateframework/tuf-conformance/pull/115#issuecomment-2275625542), the `two-level-delegations` test case triggered a wrong order. The delegations in this look as such:&lt;/p&gt;
&lt;p&gt;```python
&amp;#34;two-level-delegations&amp;#34;: DelegationsTestCase(
        delegations=[
            DelegationTester(&amp;#34;targets&amp;#34;, &amp;#34;A&amp;#34;),
            DelegationTester(&amp;#34;targets&amp;#34;, &amp;#34;B&amp;#34;),
            DelegationTester(&amp;#34;B&amp;#34;, &amp;#34;C&amp;#34;),
        ],
        visited_order=[&amp;#34;A&amp;#34;, &amp;#34;B&amp;#34;, &amp;#34;C&amp;#34;],
    ),
```&lt;/p&gt;
&lt;p&gt;Here, `targets` delegate to `&amp;#34;A&amp;#34;`, and to `&amp;#34;B&amp;#34;`, and `&amp;#34;B&amp;#34;` delegates to `&amp;#34;C&amp;#34;`. The client should trace the delegations in the order `&amp;#34;A&amp;#34;` then `&amp;#34;B&amp;#34;` then `&amp;#34;C&amp;#34;` but in this particular CI run, go-tuf traced the delegations `&amp;#34;B&amp;#34;-&amp;gt;&amp;#34;C&amp;#34;-&amp;gt;&amp;#34;A&amp;#34;`.&lt;/p&gt;
&lt;p&gt;In a subsequent CI run, this test case did not fail, but [another one did](https://github.com/theupdate…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4f8r-qqr9-fq8j</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:0350-1 — Security update for govulncheck-vulndb</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:0350-1</link>
      <description>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:0350-1</guid>
    </item>
    <item>
      <title>SUSE-SU-2024:3911-1 — Security update for govulncheck-vulndb</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2024:3911-1</link>
      <description>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for govulncheck-vulndb&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2024:3911-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-47534</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47534</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: golang-github-endophage-gotuf, Ubuntu:18.04:LTS: golang-github-endophage-gotuf&lt;/p&gt;
&lt;p&gt;go-tuf is a Go implementation of The Update Framework (TUF). The go-tuf client inconsistently traces the delegations. For example, if targets delegate to &amp;#34;A&amp;#34;, and to &amp;#34;B&amp;#34;, and &amp;#34;B&amp;#34; delegates to &amp;#34;C&amp;#34;, then the client should trace the delegations in the order &amp;#34;A&amp;#34; then &amp;#34;B&amp;#34; then &amp;#34;C&amp;#34; but it may incorrectly trace the delegations &amp;#34;B&amp;#34;-&amp;gt;&amp;#34;C&amp;#34;-&amp;gt;&amp;#34;A&amp;#34;. This vulnerability is fixed in 2.0.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: golang-github-endophage-gotuf, Ubuntu:18.04:LTS: golang-github-endophage-gotuf&lt;/p&gt;
&lt;p&gt;go-tuf is a Go implementation of The Update Framework (TUF). The go-tuf client inconsistently traces the delegations. For example, if targets delegate to &amp;#34;A&amp;#34;, and to &amp;#34;B&amp;#34;, and &amp;#34;B&amp;#34; delegates to &amp;#34;C&amp;#34;, then the client should trace the delegations in the order &amp;#34;A&amp;#34; then &amp;#34;B&amp;#34; then &amp;#34;C&amp;#34; but it may incorrectly trace the delegations &amp;#34;B&amp;#34;-&amp;gt;&amp;#34;C&amp;#34;-&amp;gt;&amp;#34;A&amp;#34;. This vulnerability is fixed in 2.0.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-47534</guid>
    </item>
  </channel>
</rss>
