EUVD-2026-31140
GHSA-7rq8-f887-2r5g
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Primary rating from Vendor (cisco) · only source for this CVE.
CVSS VectorVendor: cisco
Lifecycle Timeline
2DescriptionCVE.org
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 srchFilter configurations on custom roles.<br><br>The app contains an authorize.conf configuration file with a srchFilter entry that modifies the built-in ‘user’ role. Because the Splunk platform combines inherited search filters with the OR SPL operator, the injected filter overrides more restrictive filters on child roles.
AnalysisAI
Unauthorized data disclosure in Splunk AI Toolkit versions below 5.7.3 allows authenticated low-privileged users to bypass srchFilter-based access controls and read confidential data scoped to more restricted custom roles. The flaw stems from the Splunk platform's behavior of combining inherited search filters via the OR SPL operator, causing the permissive filter injected by the AI Toolkit's authorize.conf to override stricter filters on child roles. No active exploitation confirmed (not in CISA KEV) and no public exploit identified at time of analysis, but the CVSS confidentiality impact is rated High, making this a meaningful data exposure risk in multi-tenant or compliance-sensitive Splunk deployments.
Technical ContextAI
The vulnerability is rooted in CWE-863 (Incorrect Authorization), specifically an authorization logic flaw in how the Splunk AI Toolkit modifies the built-in 'user' role via its bundled authorize.conf configuration file. The app introduces a srchFilter entry on the 'user' role, which is a parent to custom child roles. The Splunk platform design merges inherited srchFilter values from parent and child roles using the OR SPL operator rather than AND, meaning a permissive filter anywhere in the inheritance chain widens, rather than narrows, the effective search scope. This design creates an exploitable condition where any custom role inheriting from 'user' - even one with a highly restrictive srchFilter - is effectively neutralized by the AI Toolkit's broader filter. The affected product is confirmed via CPE cpe:2.3:a:splunk:splunk_ai_toolkit:*:*:*:*:*:*:*:* across versions in the 5.7.x branch prior to 5.7.3.
RemediationAI
Upgrade Splunk AI Toolkit to version 5.7.3 or later, which resolves the srchFilter inheritance flaw in authorize.conf. The vendor patch is confirmed available per the Splunk advisory SVD-2026-0502 at https://advisory.splunk.com/advisories/SVD-2026-0502. As a compensating control prior to patching, administrators can audit and manually remove or override the AI Toolkit's srchFilter entry on the built-in 'user' role in authorize.conf - however, this change may break expected AI Toolkit search behavior and should be tested in a non-production environment first. Alternatively, organizations can restrict Splunk AI Toolkit access to users holding the 'admin' or 'power' roles only, which are explicitly excluded from the vulnerable code path, though this limits the product's utility for general users. No workaround fully replaces the patch given the inherited OR-logic behavior is a platform-level constraint.
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
Unauthenticated arbitrary file write in Splunk Enterprise (below 10.2.4 and 10.0.7) and Splunk Cloud Platform (below 10.
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10, a low-privileged user that does not hold the admin or powe
In Splunk Enterprise versions below 9.0.7 and 9.1.2, Splunk Enterprise does not safely sanitize extensible stylesheet la
In versions of Splunk Enterprise below 9.0.5, 8.2.11, and 8.1.14, and Splunk Cloud Platform below version 9.0.2303.100,
In Splunk Enterprise versions below 8.2.9, 8.1.12, and 9.0.2, an authenticated user can execute arbitrary code through t
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data t
When curl < 7.84.0 saves cookies, alt-svc and hsts data to local files, it makes the operation atomic by finalizing the
A cleartext transmission of sensitive information vulnerability exists in curl <v7.88.0 that could cause HSTS functional
When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer
A path traversal vulnerability exists in curl <8.0.0 SFTP implementation causes the tilde (~) character to be wrongly re
A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an atta
Same weakness CWE-863 – Incorrect Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today