<?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>Fri, 02 Oct 2026 20:55:47 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-378189</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-378189</link>
      <description>EUVD-2026-378189</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-378189</guid>
    </item>
    <item>
      <title>fkie_cve-2026-84465</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-84465</link>
      <description>&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;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/fkie_cve-2026-84465</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2641 — Zammad: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2641</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Zammad ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen oder sich unbefugten Zugriff auf bestehende Benutzerkonten zu verschaffen, einschließlich Agenten- und Administratorkonten.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Zammad ausnutzen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, Daten zu manipulieren, Cross-Site-Scripting-Angriffe durchzuführen oder sich unbefugten Zugriff auf bestehende Benutzerkonten zu verschaffen, einschließlich Agenten- und Administratorkonten.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2641</guid>
    </item>
  </channel>
</rss>
