<?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>Thu, 08 Oct 2026 00:46:56 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-84465 — Zammad: S/MIME signature verification allows forged sender impersonation</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-84465</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; zammad&lt;/p&gt;
&lt;p&gt;Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, when Zammad checks the digital signature on an incoming S/MIME-signed email, it does not verify that the signing certificate is genuinely trusted, it only checks whether a certificate with a matching name is already stored in the system. An attacker can create their own certificate using the name of a real, previously trusted sender and use it to send a forged email. Zammad will display that email with the same &amp;#34;validly signed&amp;#34; indicator as a genuine message from the real sender, even though the attacker never had access to that sender&amp;#39;s actual certificate or private key. This issue is fixed in version 7.1.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; zammad&lt;/p&gt;
&lt;p&gt;Zammad is a web based open source helpdesk/customer support system. Prior to 7.1.2, when Zammad checks the digital signature on an incoming S/MIME-signed email, it does not verify that the signing certificate is genuinely trusted, it only checks whether a certificate with a matching name is already stored in the system. An attacker can create their own certificate using the name of a real, previously trusted sender and use it to send a forged email. Zammad will display that email with the same &amp;#34;validly signed&amp;#34; indicator as a genuine message from the real sender, even though the attacker never had access to that sender&amp;#39;s actual certificate or private key. This issue is fixed in version 7.1.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-84465</guid>
    </item>
  </channel>
</rss>
