<?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, 24 Oct 2026 18:55:46 +0000</lastBuildDate>
    <item>
      <title>cnvd-2020-32419</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2020-32419</link>
      <description>cnvd-2020-32419</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2020-32419</guid>
    </item>
    <item>
      <title>EUVD-2026-40265</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-40265</link>
      <description>EUVD-2026-40265</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-40265</guid>
    </item>
    <item>
      <title>fkie_cve-2020-11033</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-11033</link>
      <description>&lt;p&gt;In GLPI from version 9.1 and before version 9.4.6, any API user with READ right on User itemtype will have access to full list of users when querying apirest.php/User. The response contains: - All api_tokens which can be used to do privileges escalations or read/update/delete data normally non accessible to the current user. - All personal_tokens can display another users planning. Exploiting this vulnerability requires the api to be enabled, a technician account. It can be mitigated by adding an application token. This is fixed in version 9.4.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In GLPI from version 9.1 and before version 9.4.6, any API user with READ right on User itemtype will have access to full list of users when querying apirest.php/User. The response contains: - All api_tokens which can be used to do privileges escalations or read/update/delete data normally non accessible to the current user. - All personal_tokens can display another users planning. Exploiting this vulnerability requires the api to be enabled, a technician account. It can be mitigated by adding an application token. This is fixed in version 9.4.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-11033</guid>
    </item>
    <item>
      <title>gsd-2020-11033</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-11033</link>
      <description>gsd-2020-11033</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-11033</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2020-11033</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-11033</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: glpi&lt;/p&gt;
&lt;p&gt;In GLPI from version 9.1 and before version 9.4.6, any API user with READ right on User itemtype will have access to full list of users when querying apirest.php/User. The response contains: - All api_tokens which can be used to do privileges escalations or read/update/delete data normally non accessible to the current user. - All personal_tokens can display another users planning. Exploiting this vulnerability requires the api to be enabled, a technician account. It can be mitigated by adding an application token. This is fixed in version 9.4.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: glpi&lt;/p&gt;
&lt;p&gt;In GLPI from version 9.1 and before version 9.4.6, any API user with READ right on User itemtype will have access to full list of users when querying apirest.php/User. The response contains: - All api_tokens which can be used to do privileges escalations or read/update/delete data normally non accessible to the current user. - All personal_tokens can display another users planning. Exploiting this vulnerability requires the api to be enabled, a technician account. It can be mitigated by adding an application token. This is fixed in version 9.4.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2020-11033</guid>
    </item>
  </channel>
</rss>
