Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2022-43566: Privilege bypass in Splunk Analytics Workspace risky command safeguards

Published Nov 4, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.0High · v3.1
EPSS0.93%61st percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Splunk
IdentifiersCVE-2022-43566CWE-863

CVE-2022-43566 is a security policy bypass vulnerability in Splunk Enterprise affecting versions prior to 8.1.12, 8.2.9, and 9.0.2. In the Analytics Workspace, an authenticated attacker can cause risky SPL commands to execute using a more privileged user's permissions, bypassing Splunk safeguards intended to restrict execution of risky commands. Exploitation is not fully attacker-driven and depends on social engineering: the attacker must trick a target user into initiating a crafted request in their browser. The issue affects deployments with Splunk Web enabled and is associated with abuse of Analytics Workspace request handling involving a prepositioned search context.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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 bypass Splunk's risky-command protections and execute searches under a more privileged user's effective permissions within Analytics Workspace. This can enable unauthorized access to data available to the victim account and may facilitate significant data exfiltration. The vulnerability is a privilege and policy bypass rather than direct unauthenticated code execution.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting access to Splunk Web and Analytics Workspace, especially for high-privilege users; minimize assignment of elevated roles; and harden against phishing and cross-site request initiation. Monitor audit data for suspicious Analytics Workspace searches and anomalous risky-command execution. The available information does not describe a complete vendor-supported workaround beyond applying the security update.

Remediation

Patch, then assume compromise.

Upgrade Splunk Enterprise to a fixed release: 8.1.12, 8.2.9, 9.0.2, or later, as applicable to the deployed branch. Where relevant, apply the corresponding Splunk Cloud Platform security update identified by the vendor. Vendor-provided security updates are the primary remediation.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
SplunkSplunkapplication
SplunkSplunk Cloud Platformapplication
FAQ

Frequently asked questions

Is CVE-2022-43566 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2022-43566 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-43566?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2022-43566.
Is there a patch for CVE-2022-43566?
Upgrade Splunk Enterprise to a fixed release: 8.1.12, 8.2.9, 9.0.2, or later, as applicable to the deployed branch. Where relevant, apply the corresponding Splunk Cloud Platform security update identified by the vendor.
What products are affected by CVE-2022-43566?
Splunk and Splunk Cloud Platform.
How severe is CVE-2022-43566?
CVE-2022-43566 has a CVSS v3.1 score of 8.0 (High) and an EPSS score of 0.93% (61st percentile) as of Oct 16, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.