<?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 17:54:40 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-191931</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-191931</link>
      <description>EUVD-2026-191931</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-191931</guid>
    </item>
    <item>
      <title>fkie_cve-2023-39969</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-39969</link>
      <description>&lt;p&gt;uthenticode is a small cross-platform library for partially verifying Authenticode digital signatures. Version 1.0.9 of uthenticode hashed the entire file rather than hashing sections by virtual address, in violation of the Authenticode specification. As a result, an attacker could modify code within a binary without changing its Authenticode hash, making it appear valid from uthenticode&amp;#39;s perspective. Versions of uthenticode prior to 1.0.9 are not vulnerable to this attack, nor are versions in the 2.x series. By design, uthenticode does not perform full-chain validation. However, the malleability of signature verification introduced in 1.0.9 was an unintended oversight. The 2.x series addresses the vulnerability. Versions prior to 1.0.9 are also not vulnerable, but users are encouraged to upgrade rather than downgrade. There are no workarounds to this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;uthenticode is a small cross-platform library for partially verifying Authenticode digital signatures. Version 1.0.9 of uthenticode hashed the entire file rather than hashing sections by virtual address, in violation of the Authenticode specification. As a result, an attacker could modify code within a binary without changing its Authenticode hash, making it appear valid from uthenticode&amp;#39;s perspective. Versions of uthenticode prior to 1.0.9 are not vulnerable to this attack, nor are versions in the 2.x series. By design, uthenticode does not perform full-chain validation. However, the malleability of signature verification introduced in 1.0.9 was an unintended oversight. The 2.x series addresses the vulnerability. Versions prior to 1.0.9 are also not vulnerable, but users are encouraged to upgrade rather than downgrade. There are no workarounds to this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-39969</guid>
    </item>
    <item>
      <title>gsd-2023-39969</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-39969</link>
      <description>gsd-2023-39969</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-39969</guid>
    </item>
  </channel>
</rss>
