Skip to main content
Mallory
HighVulnerability

CVE-2022-26889: Path Traversal and XSS in Splunk Enterprise <8.1.2

Published May 6, 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.8High · v3.1
EPSS1.3%71st percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Splunk
IdentifiersCVE-2022-26889CWE-22 · Improper Limitation of a Pathname…

A path traversal vulnerability exists in Splunk Enterprise versions prior to 8.1.2, where the URI path used to load relative resources within a web page can be manipulated. This allows an attacker to inject arbitrary content, such as HTML or JavaScript, into the web page (enabling XSS), or to bypass SPL safeguards for risky commands. The attack requires user interaction, typically via phishing or other social engineering to get the victim to initiate a request in their browser.

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 attacker to inject arbitrary HTML or JavaScript into the context of the Splunk web application, potentially leading to session hijacking, data exfiltration, or execution of unauthorized SPL commands. The attack is limited to scenarios where the attacker can induce the victim to make a crafted request, such as through phishing.

Mitigation

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

Restrict access to the Splunk web interface to trusted networks and users. Educate users about phishing risks and avoid clicking on suspicious links. Employ web application firewalls to detect and block malicious requests targeting path traversal or XSS vectors.

Remediation

Patch, then assume compromise.

Upgrade Splunk Enterprise to version 8.1.2 or later, where the vulnerable URI path handling has been corrected to prevent path traversal and injection attacks.

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
FAQ

Frequently asked questions

Is CVE-2022-26889 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2022-26889 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-26889?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2022-26889.
Is there a patch for CVE-2022-26889?
Upgrade Splunk Enterprise to version 8.1.2 or later, where the vulnerable URI path handling has been corrected to prevent path traversal and injection attacks.
What products are affected by CVE-2022-26889?
Splunk.
How severe is CVE-2022-26889?
CVE-2022-26889 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 1.3% (71st percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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.