<?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, 17 Oct 2026 09:01:14 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-37285 — Kibana arbitrary code execution via YAML deserialization</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-37285</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Elastic Kibana&lt;/p&gt;
&lt;p&gt;A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document containing a crafted payload. A successful attack requires a malicious user to have a combination of both specific  Elasticsearch indices privileges https://www.elastic.co/guide/en/elasticsearch/reference/current/defining-roles.html#roles-indices-priv  and  Kibana privileges https://www.elastic.co/guide/en/fleet/current/fleet-roles-and-privileges.html  assigned to them.&lt;/p&gt;
&lt;p&gt;The following Elasticsearch indices permissions are required&lt;/p&gt;
&lt;p&gt;*  write privilege on the system indices .kibana_ingest*
  *  The allow_restricted_indices flag is set to true&lt;/p&gt;
&lt;p&gt;Any of the following Kibana privileges are additionally required&lt;/p&gt;
&lt;p&gt;*  Under Fleet the All privilege is granted
  *  Under Integration the Read or All privilege is granted
  *  Access to the fleet-setup privilege is gained through the Fleet Server’s service account token&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Elastic Kibana&lt;/p&gt;
&lt;p&gt;A deserialization issue in Kibana can lead to arbitrary code execution when Kibana attempts to parse a YAML document containing a crafted payload. A successful attack requires a malicious user to have a combination of both specific  Elasticsearch indices privileges https://www.elastic.co/guide/en/elasticsearch/reference/current/defining-roles.html#roles-indices-priv  and  Kibana privileges https://www.elastic.co/guide/en/fleet/current/fleet-roles-and-privileges.html  assigned to them.&lt;/p&gt;
&lt;p&gt;The following Elasticsearch indices permissions are required&lt;/p&gt;
&lt;p&gt;*  write privilege on the system indices .kibana_ingest*
  *  The allow_restricted_indices flag is set to true&lt;/p&gt;
&lt;p&gt;Any of the following Kibana privileges are additionally required&lt;/p&gt;
&lt;p&gt;*  Under Fleet the All privilege is granted
  *  Under Integration the Read or All privilege is granted
  *  Access to the fleet-setup privilege is gained through the Fleet Server’s service account token&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-37285</guid>
    </item>
  </channel>
</rss>
