<?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 04:30:20 +0000</lastBuildDate>
    <item>
      <title>bdu:2025-04971</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2025-04971</link>
      <description>bdu:2025-04971</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2025-04971</guid>
    </item>
    <item>
      <title>EUVD-2026-228065</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-228065</link>
      <description>EUVD-2026-228065</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-228065</guid>
    </item>
    <item>
      <title>fkie_cve-2025-30401</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-30401</link>
      <description>&lt;p&gt;A spoofing issue in WhatsApp for Windows prior to version 2.2450.6 displayed attachments according to their MIME type but selected the file opening handler based on the attachment’s filename extension. A maliciously crafted mismatch could have caused the recipient to inadvertently execute arbitrary code rather than view the attachment when manually opening the attachment inside WhatsApp. We have not seen evidence of exploitation in the wild.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A spoofing issue in WhatsApp for Windows prior to version 2.2450.6 displayed attachments according to their MIME type but selected the file opening handler based on the attachment’s filename extension. A maliciously crafted mismatch could have caused the recipient to inadvertently execute arbitrary code rather than view the attachment when manually opening the attachment inside WhatsApp. We have not seen evidence of exploitation in the wild.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-30401</guid>
    </item>
    <item>
      <title>GHSA-hp4v-q7qc-45wr</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hp4v-q7qc-45wr</link>
      <description>&lt;p&gt;A spoofing issue in WhatsApp for Windows prior to version 2.2450.6 displayed attachments according to their MIME type but selected the file opening handler based on the attachment’s filename extension. A maliciously crafted mismatch could have caused the recipient to inadvertently execute arbitrary code rather than view the attachment when manually opening the attachment inside WhatsApp.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A spoofing issue in WhatsApp for Windows prior to version 2.2450.6 displayed attachments according to their MIME type but selected the file opening handler based on the attachment’s filename extension. A maliciously crafted mismatch could have caused the recipient to inadvertently execute arbitrary code rather than view the attachment when manually opening the attachment inside WhatsApp.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hp4v-q7qc-45wr</guid>
    </item>
  </channel>
</rss>
