<?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://db.gcve.eu</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, 20 Nov 2026 01:54:58 +0000</lastBuildDate>
    <item>
      <title>certfr-2026-avi-1576 — De multiples vulnérabilités ont été découvertes dans les produits Splunk. Certaines d'entre elles permettent à un attaq…</title>
      <link>https://db.gcve.eu/vuln/certfr-2026-avi-1576</link>
      <description>certfr-2026-avi-1576</description>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/certfr-2026-avi-1576</guid>
    </item>
    <item>
      <title>fkie_cve-2026-131305</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-131305</link>
      <description>&lt;p&gt;In Splunk AI Assistant versions below 2.0.0, a user who does not hold the &amp;#34;admin&amp;#34; or &amp;#34;power&amp;#34; Splunk roles could submit client-controlled feature settings through the Representational State Transfer (REST) API. This could modify limited response metadata outside the expected server-side configuration.
The vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Splunk AI Assistant versions below 2.0.0, a user who does not hold the &amp;#34;admin&amp;#34; or &amp;#34;power&amp;#34; Splunk roles could submit client-controlled feature settings through the Representational State Transfer (REST) API. This could modify limited response metadata outside the expected server-side configuration.
The vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-131305</guid>
    </item>
    <item>
      <title>GHSA-84hp-vf92-h67x</title>
      <link>https://db.gcve.eu/vuln/ghsa-84hp-vf92-h67x</link>
      <description>&lt;p&gt;In Splunk AI Assistant versions below 2.0.0, a user who does not hold the &amp;#34;admin&amp;#34; or &amp;#34;power&amp;#34; Splunk roles could submit client-controlled feature settings through the Representational State Transfer (REST) API. This could modify limited response metadata outside the expected server-side configuration.
The vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Splunk AI Assistant versions below 2.0.0, a user who does not hold the &amp;#34;admin&amp;#34; or &amp;#34;power&amp;#34; Splunk roles could submit client-controlled feature settings through the Representational State Transfer (REST) API. This could modify limited response metadata outside the expected server-side configuration.
The vulnerability is possible because the REST API processes client-supplied feature settings without enforcing the expected server-side configuration boundary.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-84hp-vf92-h67x</guid>
    </item>
  </channel>
</rss>
