Loading story…
Splunk disclosed a critical vulnerability in Splunk AI Toolkit that allows OS command injection through the btool Configuration Helper, affecting versions earlier than 5.7.4. Tracked as CVE-2026-20266 and rated CVSS 9.1, the flaw stems from unsafe shell execution that can let a user with the Splunk admin role run arbitrary commands on the host running Splunk Enterprise, creating a direct path to host compromise.
Splunk also fixed CVE-2026-20265, a lower-severity insecure default domain allowlist issue rated CVSS 4.3 that could allow a low-privileged user to trigger outbound HTTP requests and potentially exfiltrate data to an attacker-controlled server. The Canadian Centre for Cyber Security highlighted the vendor advisory in AV26-614 and urged administrators to review Splunk’s guidance and upgrade to version 5.7.4 or later; public reporting said there was no confirmed exploitation in the wild at disclosure time.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
On 2026-06-18, Atlassian announced security updates covering dozens of vulnerabilities across multiple Data Center and Server products, largely tied to third-party dependencies such as Axios, Apache Tomcat, and Netty. The company addressed several critical-severity CVEs through product updates and urged users to upgrade promptly.
On 2026-06-17, the Canadian Centre for Cyber Security published advisory AV26-614 highlighting Splunk's security update, including the critical Splunk AI Toolkit issue. The advisory urged users and administrators to review Splunk's advisories and apply the necessary updates.
On 2026-06-17, Splunk published security advisories for vulnerabilities in Splunk AI Toolkit, including CVE-2026-20266, a critical OS command injection flaw in the btool Configuration Helper affecting versions earlier than 5.7.4. The advisories indicate the issues are fixed in version 5.7.4 and users should apply the update.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
11 references tracked. Mallory keeps watching after this page renders.
securityweek.com
Open sourcecybersecuritynews.com
Open sourcemalware.news
Open sourcesecurityonline.info
Open sourceadvisory.splunk.com
Open sourcecve.org
Open sourceconfluence.atlassian.com
Open sourcecwe.mitre.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Splunk disclosed and fixed **CVE-2026-20266**, a critical OS command injection flaw in the Splunk AI Toolkit's `btool` configuration helper that can let a user with the **Splunk admin role** execute arbitrary operating system commands on the underlying host. The vulnerability is classified as **CWE-78** and carries a **CVSS 9.1** score; it stems from unsafe shell execution in which dynamic parameters are concatenated into a shell-interpreted command string, potentially allowing injected commands to run with the privileges of the `splunkd` service account. The issue affects **Splunk AI Toolkit versions earlier than 5.7.4** in the 5.7.x branch and requires the AI Toolkit to be installed and active for exploitation. Splunk addressed the flaw in **version 5.7.4**, and downstream security notices have highlighted the update as part of broader Splunk security guidance. Reporting on the bug also noted similarities to **CVE-2026-20163**, pointing to a recurring risk pattern around shell interpretation in privileged Splunk components.
Jul 10, 2026
Splunk released patches for three vulnerabilities affecting **Splunk Enterprise**, **Splunk Cloud Platform**, and the **Splunk AI Toolkit**, including a high-severity denial-of-service bug and two issues that can expose sensitive data. `CVE-2026-20240` affects the `splunk_archiver` app, where a low-privileged user can abuse the `coldToFrozen.sh` script to rename critical directories and render an instance inoperable. `CVE-2026-20239` stems from improper output sanitization in the TcpChannel component and can leak session cookies and cleartext HTTP response bodies into the `_internal` log index, while `CVE-2026-20238` is an access-control weakness in the Splunk AI Toolkit that can bypass intended search restrictions and expose restricted data. Splunk said the issues were fixed in updated releases, including **AI Toolkit 5.7.3** for `CVE-2026-20238`, and urged customers to upgrade affected deployments. The company also published interim mitigations for organizations that cannot patch immediately, including restricting access to the `_internal` index to administrators, disabling the **Splunk Archiver** application, reviewing inherited roles and permissions, and removing the problematic `srchFilter` entry from local configuration where applicable. The advisories highlight risks to both platform availability and the confidentiality of operational data stored in Splunk environments.
Jun 29, 2026
Splunk released security updates for multiple vulnerabilities in **Splunk Enterprise** and **Splunk Cloud Platform**, led by **`CVE-2026-20296`**, a high-severity flaw in the Deployment Server component of Splunk Web. The bug combines missing CSRF validation on `GET` requests with improper neutralization of user-controlled input, allowing an attacker to trick a user with the `list_deployment_server` capability into triggering arbitrary SPL searches as `splunk-system-user`. Successful exploitation could expose indexed data and stored credentials, with additional integrity and limited availability impact. The update also addresses **`CVE-2026-20297`** in the App Install REST endpoint and **`CVE-2026-20298`** in the `storage/passwords` REST endpoint, which could enable path traversal and disclosure of stored credential hashes. Splunk published patched versions and mitigation guidance for customers, while **Splunk Cloud Platform** instances are being patched and monitored by Splunk. **Splunk Enterprise** administrators were advised to upgrade promptly and apply a configuration change to reduce exposure from the credential-hash disclosure issue.
Jul 17, 2026