<rss version="2.0">  
	<channel>  
		<title>Splunk Security Announcements</title>  
		<link>https://advisory.splunk.com/feed.xml</link>  
		<description>Splunk Security Announcements</description>  
		<language>en</language>  
		<copyright>2023 Splunk</copyright>  
		
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0701: Third-Party Package Updates in Python for Scientific Computing - July 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Python for Scientific Computing version 4.3.2 and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 01 Jul 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0701</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0614: OS Command Injection in the btool Configuration Helper in Splunk AI Toolkit]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk AI Toolkit versions below 5.7.4, a user who holds the “admin” Splunk role could execute arbitrary OS commands on the host running the Splunk Enterprise instance.</p>

<p>The vulnerability is possible because of an unsafe shell execution pattern in the btool configuration helper, which constructs OS command strings from dynamic parameters without disabling shell interpretation.</p>
]]>  
				</description> 
				<pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0614</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0613: Insecure Default Domain Allowlist in Splunk AI Toolkit]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk AI Toolkit versions below 5.7.4, a low-privileged user that does not hold the “admin” or “power” Splunk roles could cause the Splunk AI Toolkit to make outbound requests over HTTP to a server that an attacker controls, which could allow for data exfiltration.</p>

<p>The vulnerability exists because of an insecure default domain allowlist in the Splunk AI Toolkit, which does not restrict outbound AI agent  requests to approved external domains.</p>
]]>  
				</description> 
				<pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0613</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0612: Third-Party Package Updates in Splunk SOAR - June 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk SOAR version 8.5.0, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0612</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0611: Log Injection through HTTP Request Paths in Splunk SOAR]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk SOAR (Security Orchestration, Automation, and Response) versions below 8.5.0, an unauthenticated attacker could inject American National Standards Institute (ANSI) escape codes into SOAR application log files through specially crafted HTTP request paths, which a terminal emulator might interpret when an administrator views the logs.<br /><br />The injection is possible because SOAR does not strip control characters from HTTP request paths before writing them to application logs.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0611</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0610: Third-Party Package Updates in Splunk Enterprise - June 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk Enterprise versions 10.4.0, 10.2.4, 10.0.7, 9.4.12, 9.3.13, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0610</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0609: Improper Access Control in Splunk Enterprise]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.4 and 10.0.7, and Splunk Cloud Platform versions below 10.4.2604.0, 10.3.2512.12, 10.2.2510.15, 10.1.2507.23, 10.0.2503.14, and 9.3.2411.131, a user who holds a Splunk role that contains the high-privilege capability <code class="language-plaintext highlighter-rouge">edit_saved_search_owner</code> could reassign saved search ownership to users outside their authorized scope. The ownership reassignment endpoint lacks access control.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0609</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0608: Stored Cross-Site Scripting (XSS) through Classic Dashboard in Splunk Enterprise]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.11, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the “admin” or “power” Splunk roles could store a malicious script in a classic dashboard HTML panel, causing unauthorized JavaScript code to execute in the browser of another user.</p>

<p>The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The low-privileged user should not be able to exploit the vulnerability at will.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0608</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0607: Improper Input Validation through Classic Dashboard CSS in Splunk Enterprise]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the “admin” or “power” Splunk roles could craft a classic dashboard that exfiltrates sensitive data from the browser of a higher-privileged user who views it.</p>

<p>The exfiltration is possible because classic dashboard panels do not fully validate style attribute values, which can allow for requests to reach external domains outside the configured Trusted Domains List.</p>

<p>The vulnerability requires the attacker to phish the victim by tricking them into initiating a request within their browser. The low-privileged user should not be able to exploit the vulnerability at will.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0607</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0606: Improper Input Validation through Protocol-Relative URL in Classic Dashboards in Splunk Enterprise]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the ‘admin’ or ‘power’ Splunk roles could cause data exfiltration through classic dashboards by redirecting a victim to an external site using a protocol-relative URL in a drill-down link.<br /><br />The vulnerability exists because the URL classifier in classic dashboards only recognizes <code class="language-plaintext highlighter-rouge">http://</code> and <code class="language-plaintext highlighter-rouge">https://</code> schemes when checking for external URLs. Protocol-relative URLs such as <code class="language-plaintext highlighter-rouge">//attacker.com</code> bypass this check entirely, and Splunk Web does not show the external-navigation warning dialog to the victim.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0606</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0605: Improper Input Validation through Classic Dashboards in Splunk Enterprise]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the “admin” or “power” Splunk roles could craft a malicious classic dashboard that exfiltrates sensitive data to an external server.</p>

<p>The vulnerability exists because URL validation on the external content dialog is incomplete, which can allow for requests to untrusted domains when a user interacts with a crafted dashboard.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0605</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0604: Information Disclosure through External Content Restriction Bypass in Splunk Enterprise]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.3.2512.13, 10.2.2510.15, 10.1.2507.23, and 9.3.2411.132, a low-privileged user that does not hold the ‘admin’ or ‘power’ Splunk roles could craft a malicious classic dashboard that exfiltrates sensitive data to an external server when a higher-privileged user views it, bypassing the external content restriction through a Cascading Style Sheets (CSS) injection.<br /><br />The Trusted Domains security check does not fully validate inline style attribute values, which can allow for outbound requests to untrusted domains and credential exfiltration when a victim views a crafted dashboard.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0604</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0603: Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk Enterprise]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.4 and 10.0.7, an unauthenticated user could create or truncate arbitrary files through a PostgreSQL sidecar service endpoint.<br /><br />The vulnerability exists because the PostgreSQL sidecar service endpoint lacks authentication controls, allowing any network-reachable user to invoke file operations without credentials.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0603</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0602: Server-Side Request Forgery (SSRF) through Dashboard Studio PDF Export in Splunk Enterprise]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, and Splunk Cloud Platform versions below 10.4.2604.3, 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, a low-privileged user that does not hold the “admin” or “power” Splunk roles could send server-side requests to arbitrary internal destinations through the Dashboard Studio PDF export feature.</p>

<p>The vulnerability exists because the trusted-domain validation uses a prefix match that can be bypassed with attacker-controlled subdomains (for example, docs.splunk.com.evil.com), and because the PDF export service follows HTTP redirects automatically without re-validating each redirect target against the allowlist.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0602</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0601: Remote Code Execution through Deserialization of Untrusted Data in Splunk Secure Gateway]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.4, 10.0.7, 9.4.12, and 9.3.13, Splunk Cloud Platform versions below 10.3.2512.12, 10.2.2510.14, 10.1.2507.22, and 9.3.2411.132, and Splunk Secure Gateway versions below 3.10.6, 3.9.20, and 3.8.67, a low-privileged user that does not hold the ‘admin’ or ‘power’ Splunk roles could perform a Remote Code Execution (RCE) through the Splunk Secure Gateway app.<br /><br />The Remote Code Execution is possible because of unsafe deserialization of App Key Value Store (KV Store) data through the ‘jsonpickle’ Python library, which reconstructs arbitrary Python objects from specially crafted JavaScript Object Notation (JSON) without adequate validation.</p>
]]>  
				</description> 
				<pubDate>Wed, 10 Jun 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0601</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0516: Third-Party Package Updates in Splunk Add-on for Tomcat App - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk Add-on for Tomcat App version 3.3.1 and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0516</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0515: Third-Party Package Updates in Splunk User Behavior Analytics - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk User Behavior Analytics versions 5.4.5, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0515</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0514: Third-Party Package Updates in Splunk AppDynamics Machine Agent - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk AppDynamics Machine Agent version 26.4.0, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0514</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0513: Third-Party Package Updates in Splunk AppDynamics Java Agent - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk AppDynamics Java Agent version 26.4.0, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0513</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0512: Third-Party Package Updates in Splunk AppDynamics Private Synthetic Agent (PSA) - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk AppDynamics Private Synthetic Agent version 26.4.0, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0512</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0511: Third-Party Package Updates in Splunk AppDynamics Python Agent - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk AppDynamics Python Agent version 26.4.1, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0511</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0510: Third-Party Package Updates in Splunk AppDynamics Cluster Agent - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk AppDynamics Cluster Agent version 26.4.0, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0510</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0509: Third-Party Package Updates in Splunk AppDynamics Database Agent - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk AppDynamics Database Agent version 26.4.0, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0509</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0508: Third-Party Package Updates in Splunk AppDynamics Analytics Agent - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk AppDynamics Analytics Agent version 26.4.0, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0508</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0507: Third-Party Package Updates in Splunk AppDynamics Apache Web Server Agent - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk AppDynamics Apache Web Server Agent version 25.11.1, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0507</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0506: Third-Party Package Updates in Splunk Universal Forwarder - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk Universal Forwarder versions 9.4.11, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0506</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0505: Third-Party Package Updates in Splunk Enterprise - May 2026]]>  
				</title>  
				<description>  
					<![CDATA[<p>Splunk remedied common vulnerabilities and exposures (CVEs) in Third Party Packages in Splunk Enterprise versions 10.2.3, 10.0.6, 9.4.11, 9.3.12, and higher.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0505</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0504: Denial of Service through coldToFrozen.sh Script in Splunk Enterprise]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.2, 10.0.5, 9.4.11, and 9.3.12, a low-privileged user that does not hold the ‘admin’ or ‘power’ Splunk roles could cause a Denial of Service by exploiting the <code class="language-plaintext highlighter-rouge">coldToFrozen.sh</code> script in the <code class="language-plaintext highlighter-rouge">splunk_archiver</code> app to rename critical Splunk directories, making the instance non-functional.<br /><br />The Denial of Service is possible because of missing input validation in the <code class="language-plaintext highlighter-rouge">coldToFrozen.sh</code> script, which accepts arbitrary file paths and renames them without restricting operations to safe directories.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0504</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0503: Sensitive Information Disclosure through Log Files in Splunk Enterprise]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk Enterprise versions below 10.2.2 and 10.0.5, and Splunk Cloud Platform versions below 10.3.2512.8, 10.2.2510.11, 10.1.2507.21, and 10.0.2503.13, a user with a role that has access to the <code class="language-plaintext highlighter-rouge">_internal</code> index could view session cookies and response bodies that contain sensitive data.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0503</link>
				<category>Security Advisory</category>  
			</item>  
		
			<item>  
				<title>  
					<![CDATA[SVD-2026-0502: Improper Access Control through Role Inheritance in Splunk AI Toolkit app]]>  
				</title>  
				<description>  
					<![CDATA[<p>In Splunk AI Toolkit versions below 5.7.3, a low-privileged user that does not hold the ‘admin’ or ‘power’ roles could access confidential data that was restricted through <code class="language-plaintext highlighter-rouge">srchFilter</code> configurations on custom roles.<br /><br />The app contains an <code class="language-plaintext highlighter-rouge">authorize.conf</code> configuration file with a <code class="language-plaintext highlighter-rouge">srchFilter</code> entry that modifies the built-in ‘user’ role. Because the Splunk platform combines inherited search filters with the <code class="language-plaintext highlighter-rouge">OR</code> SPL operator, the injected filter overrides more restrictive filters on child roles.</p>
]]>  
				</description> 
				<pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate>  
				   
				<link>https://advisory.splunk.com//advisories/SVD-2026-0502</link>
				<category>Security Advisory</category>  
			</item>  
		 
	</channel>  
</rss>   
