<?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:08:33 +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-76543</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-76543</link>
      <description>&lt;p&gt;In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the &amp;#34;power&amp;#34; Splunk role could store attacker-controlled Search Processing Language (SPL) in a shared data model.
The vulnerability is possible because the Data Model Editor does not properly neutralize data model field names when it builds a preview search.
The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker should not be able to exploit the vulnerability at will.
For more information see Add a regular expression field (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/define-data-model-dataset-fields/add-a-regular-expression-field), Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and About the search language (https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.4/search-overview/about-the-search-language) in the Splunk documentation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the &amp;#34;power&amp;#34; Splunk role could store attacker-controlled Search Processing Language (SPL) in a shared data model.
The vulnerability is possible because the Data Model Editor does not properly neutralize data model field names when it builds a preview search.
The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker should not be able to exploit the vulnerability at will.
For more information see Add a regular expression field (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/define-data-model-dataset-fields/add-a-regular-expression-field), Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and About the search language (https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.4/search-overview/about-the-search-language) in the Splunk documentation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-76543</guid>
    </item>
    <item>
      <title>GHSA-5whp-r82m-9r26</title>
      <link>https://db.gcve.eu/vuln/ghsa-5whp-r82m-9r26</link>
      <description>&lt;p&gt;In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the &amp;#34;power&amp;#34; Splunk role could store attacker-controlled Search Processing Language (SPL) in a shared data model.
The vulnerability is possible because the Data Model Editor does not properly neutralize data model field names when it builds a preview search.
The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker should not be able to exploit the vulnerability at will.
For more information see Add a regular expression field (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/define-data-model-dataset-fields/add-a-regular-expression-field), Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and About the search language (https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.4/search-overview/about-the-search-language) in the Splunk documentation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Splunk Enterprise versions below 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17, a user who holds the &amp;#34;power&amp;#34; Splunk role could store attacker-controlled Search Processing Language (SPL) in a shared data model.
The vulnerability is possible because the Data Model Editor does not properly neutralize data model field names when it builds a preview search.
The vulnerability requires the attacker to phish the affected user by tricking them into initiating a request within their browser. The attacker should not be able to exploit the vulnerability at will.
For more information see Add a regular expression field (https://help.splunk.com/en/splunk-enterprise/manage-knowledge-objects/knowledge-management-manual/10.4/define-data-model-dataset-fields/add-a-regular-expression-field), Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.4/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities), and About the search language (https://help.splunk.com/en/splunk-enterprise/search/search-manual/10.4/search-overview/about-the-search-language) in the Splunk documentation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-5whp-r82m-9r26</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4674 — Splunk Enterprise: Mehrere Schwachstellen</title>
      <link>https://db.gcve.eu/vuln/wid-sec-w-2026-4674</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Splunk Enterprise ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, Daten zu manipulieren, einen Denial-of-Service-Zustand zu verursachen oder seine Rechte zu erweitern.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Splunk Enterprise ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, Daten zu manipulieren, einen Denial-of-Service-Zustand zu verursachen oder seine Rechte zu erweitern.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/wid-sec-w-2026-4674</guid>
    </item>
  </channel>
</rss>
