<?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>Tue, 06 Oct 2026 03:14:41 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-243054</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-243054</link>
      <description>EUVD-2026-243054</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-243054</guid>
    </item>
    <item>
      <title>fkie_cve-2025-46339</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-46339</link>
      <description>&lt;p&gt;FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, it&amp;#39;s possible to poison feed favicons by adding a given URL as a feed with the proxy set to an attacker-controlled one and disabled SSL verifying. The favicon hash is computed by hashing the feed URL and the salt, whilst not including the following variables: proxy address, proxy protocol, and whether SSL should be verified. Therefore it&amp;#39;s possible to poison a favicon of a given feed by simply intercepting the response of the feed, and changing the website URL to one where a threat actor controls the feed favicon. Feed favicons can be replaced for all users by anyone. Version 1.26.2 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;FreshRSS is a self-hosted RSS feed aggregator. Prior to version 1.26.2, it&amp;#39;s possible to poison feed favicons by adding a given URL as a feed with the proxy set to an attacker-controlled one and disabled SSL verifying. The favicon hash is computed by hashing the feed URL and the salt, whilst not including the following variables: proxy address, proxy protocol, and whether SSL should be verified. Therefore it&amp;#39;s possible to poison a favicon of a given feed by simply intercepting the response of the feed, and changing the website URL to one where a threat actor controls the feed favicon. Feed favicons can be replaced for all users by anyone. Version 1.26.2 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-46339</guid>
    </item>
  </channel>
</rss>
