<?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>Wed, 07 Oct 2026 17:41:05 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-214509</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-214509</link>
      <description>EUVD-2026-214509</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-214509</guid>
    </item>
    <item>
      <title>fkie_cve-2024-56169</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-56169</link>
      <description>&lt;p&gt;A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-56169</guid>
    </item>
    <item>
      <title>GHSA-pggg-fp6x-7ww3</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pggg-fp6x-7ww3</link>
      <description>&lt;p&gt;A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pggg-fp6x-7ww3</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-56169</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56169</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: fort-validator, Ubuntu:22.04:LTS: fort-validator, Ubuntu:Pro:24.04:LTS: fort-validator, Ubuntu:25.10: fort-validator, Ubuntu:26.04:LTS: fort-validator&lt;/p&gt;
&lt;p&gt;A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: fort-validator, Ubuntu:22.04:LTS: fort-validator, Ubuntu:Pro:24.04:LTS: fort-validator, Ubuntu:25.10: fort-validator, Ubuntu:26.04:LTS: fort-validator&lt;/p&gt;
&lt;p&gt;A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-56169</guid>
    </item>
  </channel>
</rss>
