<?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:10:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-131194 — Stored Cross-Site Scripting (XSS) through Splunk Web Views in Splunk Enterprise</title>
      <link>https://db.gcve.eu/vuln/cve-2026-131194</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Splunk Enterprise&lt;/p&gt;
&lt;p&gt;In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a low-privileged user who holds the &amp;#34;power&amp;#34; Splunk role could inject malicious content into a Splunk Web view. When another authenticated user opens the affected view in Splunk Web, the injected content executes unauthorized JavaScript code within the viewing user&amp;#39;s browser session.
The vulnerability is possible because Splunk Web does not properly validate content in a view definition before rendering the view.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Splunk Enterprise&lt;/p&gt;
&lt;p&gt;In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, a low-privileged user who holds the &amp;#34;power&amp;#34; Splunk role could inject malicious content into a Splunk Web view. When another authenticated user opens the affected view in Splunk Web, the injected content executes unauthorized JavaScript code within the viewing user&amp;#39;s browser session.
The vulnerability is possible because Splunk Web does not properly validate content in a view definition before rendering the view.
For more information see Define roles on the Splunk platform with capabilities (https://help.splunk.com/en/splunk-enterprise/administer/manage-users-and-security/10.2/manage-splunk-platform-users-and-roles/define-roles-on-the-splunk-platform-with-capabilities) in the Splunk documentation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-131194</guid>
    </item>
  </channel>
</rss>
