<?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 12:05:22 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1039 — De multiples vulnérabilités ont été découvertes dans Zabbix. Certaines d'entre elles permettent à un attaquant de provo…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1039</link>
      <description>certfr-2026-avi-1039</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1039</guid>
    </item>
    <item>
      <title>EUVD-2026-355277</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-355277</link>
      <description>EUVD-2026-355277</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-355277</guid>
    </item>
    <item>
      <title>fkie_cve-2026-23933</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-23933</link>
      <description>&lt;p&gt;In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-23933</guid>
    </item>
    <item>
      <title>GHSA-5j5m-c26m-fvc8</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5j5m-c26m-fvc8</link>
      <description>&lt;p&gt;In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5j5m-c26m-fvc8</guid>
    </item>
    <item>
      <title>NCSC-2026-0320 — Kwetsbaarheden verholpen in Zabbix</title>
      <link>https://cve.radiocsirt.org/vuln/ncsc-2026-0320</link>
      <description>NCSC-2026-0320</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ncsc-2026-0320</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-23933</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23933</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: zabbix, Ubuntu:Pro:16.04:LTS: zabbix, Ubuntu:Pro:18.04:LTS: zabbix, Ubuntu:Pro:20.04:LTS: zabbix, Ubuntu:Pro:22.04:LTS: zabbix, Ubuntu:26.04:LTS: zabbix&lt;/p&gt;
&lt;p&gt;In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: zabbix, Ubuntu:Pro:16.04:LTS: zabbix, Ubuntu:Pro:18.04:LTS: zabbix, Ubuntu:Pro:20.04:LTS: zabbix, Ubuntu:Pro:22.04:LTS: zabbix, Ubuntu:26.04:LTS: zabbix&lt;/p&gt;
&lt;p&gt;In Zabbix 7.4 the cryptographic key used for signing Frontend sessions has been erroneously written to the database seed. Currently the only known exploitation scenario is for deployments that utilize both - SAML authentication and guest users. In such cases the key can be used to forge valid session cookies, potentially leading to unauthorized access. For other Zabbix deployments this does not have a known impact.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-23933</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2916 — Zabbix: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2916</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Zabbix ausnutzen, um Informationen offenzulegen oder zu manipulieren, um Sicherheitsmechanismen zu umgehen, um einen Denial of Service herbeizuführen, um einen Cross-Site Scripting Angriff durchzuführen und potenziell um Code auszuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Zabbix ausnutzen, um Informationen offenzulegen oder zu manipulieren, um Sicherheitsmechanismen zu umgehen, um einen Denial of Service herbeizuführen, um einen Cross-Site Scripting Angriff durchzuführen und potenziell um Code auszuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2916</guid>
    </item>
  </channel>
</rss>
