Loading vulnerability…
Improper Access Control in Splunk AI Toolkit Role Inheritance
CVE-2026-20238 is an improper access control vulnerability in Splunk AI Toolkit versions prior to 5.7.3. The issue is caused by a default authorize.conf configuration that includes an srchFilter entry modifying Splunk’s built-in user role. In Splunk, inherited search filters are combined using the logical OR operator in SPL. Because of this behavior, the AI Toolkit’s injected filter can negate or override more restrictive srchFilter constraints applied to descendant custom roles. As a result, users who do not hold the admin or power roles but inherit from the affected built-in role can bypass intended search restrictions and access data that should remain limited by custom role-based filtering.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows low-privileged authenticated users to bypass role-based search restrictions and view confidential or otherwise restricted datasets. The primary impact is unauthorized disclosure of sensitive information within Splunk-accessible data sources. The flaw weakens tenant or organizational data segregation enforced through custom srchFilter policies and can expose corporate data to users who should not be able to retrieve it.
If you can’t patch tonight, do this now.
If immediate upgrading is not possible, disable the Splunk AI Toolkit or remove or override the problematic srchFilter entry from the application’s authorization configuration so it no longer modifies the built-in user role. Because changing this setting may broaden access to AI Toolkit-related indexes if not carefully controlled, administrators should validate resulting permissions and apply explicit restrictions where needed. Additional review of custom role inheritance and effective search filters is advisable until the product is upgraded.
Patch, then assume compromise.
Upgrade Splunk AI Toolkit to version 5.7.3 or later, which removes or corrects the problematic role configuration. Review role inheritance and all custom srchFilter definitions after upgrading to confirm that effective search restrictions behave as intended and that no inherited filter logic continues to broaden access unexpectedly.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.