Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Medium

Improper access control in Splunk AI Toolkit role search filter inheritance

IdentifiersCVE-2026-20238CWE-284

CVE-2026-20238 affects Splunk AI Toolkit versions below 5.7.3. The vulnerability is caused by the app shipping an authorize.conf file containing an srchFilter entry that modifies Splunk's built-in user role. In Splunk, inherited search filters are combined using the logical OR operator in SPL. Because of that behavior, the AI Toolkit's injected filter on the parent user role can override or negate more restrictive srchFilter constraints configured on child custom roles. As a result, users who do not hold the admin or power roles can bypass intended search restrictions and access data that should remain restricted by custom role-based search filters.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in unauthorized disclosure of data within Splunk. Low-privileged users may be able to bypass explicit access controls implemented through custom-role srchFilter restrictions and view confidential corporate datasets or other sensitive indexed data. The issue is an access-control bypass and data exposure problem rather than code execution or privilege escalation on the host.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, disable the Splunk AI Toolkit or remove/override the problematic srchFilter line from the app's local configuration so it no longer modifies the built-in user role. Because the provided context notes that this workaround may broaden access to ai_agent_run_history_index, administrators should apply additional restrictions as needed and validate effective permissions after any configuration change.

Remediation

Patch, then assume compromise.

Upgrade Splunk AI Toolkit to version 5.7.3 or later, which fixes the vulnerable default configuration. Review role inheritance and srchFilter behavior in affected deployments to ensure custom roles still enforce the intended search restrictions after upgrade.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SplunkAi Toolkitapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.