CVE-2022-43567: Authenticated RCE in Splunk Secure Gateway Mobile Alerts
- Vendor
- Splunk
CVE-2022-43567 is a remote command execution vulnerability in the Splunk Secure Gateway app’s mobile alerts feature affecting Splunk Enterprise versions earlier than 8.1.12, 8.2.9, and 9.0.2. An authenticated user can send specially crafted requests to the mobile alerts functionality and cause arbitrary operating system commands to be executed remotely by the Splunk instance. The vulnerable attack surface is associated with the mobile alerts endpoint exposed through the Splunk Secure Gateway app. The issue is consistent with improper neutralization of special elements in an OS command, enabling attacker-controlled input to reach command execution logic.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows an authenticated attacker to execute arbitrary operating system commands on the target Splunk Enterprise system remotely. This can lead to full compromise of the affected Splunk environment, including unauthorized code execution, alteration of system state or indexed data, abuse of the Splunk server as a foothold for lateral movement, disruption of services, and access to sensitive information available to the Splunk process and host.
Mitigation
If you can’t patch tonight, do this now.
No specific workaround is available in the provided information. Until patching is completed, reduce exposure by restricting access to Splunk management and application interfaces, limiting or disabling use of the Splunk Secure Gateway app and its mobile alerts feature where operationally feasible, and ensuring only tightly controlled authenticated users can reach the vulnerable functionality. Monitoring for suspicious requests targeting the mobile alerts feature can help identify exploitation attempts but is not a substitute for patching.
Remediation
Patch, then assume compromise.
Upgrade Splunk Enterprise to a fixed release. Affected versions earlier than 8.1.12, 8.2.9, and 9.0.2 should be updated to 8.1.12, 8.2.9, 9.0.2, or later as appropriate for the deployment branch. Where applicable, Splunk Cloud Platform 9.0.x deployments earlier than 9.0.2211 should be upgraded to 9.0.2211 or later. Apply the vendor-provided security update referenced in the November 2022 Splunk security bulletin.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
Frequently asked questions
- Is CVE-2022-43567 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2022-43567 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2022-43567?
- Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2022-43567.
- Is there a patch for CVE-2022-43567?
- Upgrade Splunk Enterprise to a fixed release. Affected versions earlier than 8.1.12, 8.2.9, and 9.0.2 should be updated to 8.1.12, 8.2.9, 9.0.2, or later as appropriate for the deployment branch.
- What products are affected by CVE-2022-43567?
- Splunk and Splunk Cloud Platform.
- How severe is CVE-2022-43567?
- CVE-2022-43567 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 1.4% (73rd percentile) as of Oct 16, 2026.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.