<?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 12:08:41 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-376420</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-376420</link>
      <description>EUVD-2026-376420</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-376420</guid>
    </item>
    <item>
      <title>fkie_cve-2026-56727</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-56727</link>
      <description>&lt;p&gt;Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, summary In Zammad&amp;#39;s inbound PGP email processing, the return value of the gpg verification call was silently discarded. Regardless of whether gpg reported a valid, invalid, or missing signature, the handler unconditionally wrote sign: { success: true, comment: &amp;#34;Good signature&amp;#34; } to the article&amp;#39;s security preferences. Impact Any sender could tamper with the body of a multipart/signed PGP email, or craft a message with an entirely fabricated or mismatched signature, and Zammad would display it to the recipient as cryptographically verified with a &amp;#34;Good signature&amp;#34; label. Users and agents relying on Zammad&amp;#39;s signature indicator to confirm message authenticity and integrity would be misled into trusting modified or forged content. The vulnerability affects all inbound PGP-signed emails processed while the PGP integration is enabled. This issue is fixed in version 7.0.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, summary In Zammad&amp;#39;s inbound PGP email processing, the return value of the gpg verification call was silently discarded. Regardless of whether gpg reported a valid, invalid, or missing signature, the handler unconditionally wrote sign: { success: true, comment: &amp;#34;Good signature&amp;#34; } to the article&amp;#39;s security preferences. Impact Any sender could tamper with the body of a multipart/signed PGP email, or craft a message with an entirely fabricated or mismatched signature, and Zammad would display it to the recipient as cryptographically verified with a &amp;#34;Good signature&amp;#34; label. Users and agents relying on Zammad&amp;#39;s signature indicator to confirm message authenticity and integrity would be misled into trusting modified or forged content. The vulnerability affects all inbound PGP-signed emails processed while the PGP integration is enabled. This issue is fixed in version 7.0.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-56727</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1981 — Zammad: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1981</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Zammad ausnutzen, um Administratorrechte zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Zammad ausnutzen, um Administratorrechte zu erlangen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1981</guid>
    </item>
  </channel>
</rss>
