Skip to main content
Mallory
MediumVulnerability

CVE-2026-76287: Ownership authorization bypass in Splunk Enterprise SPL2 preview jobs

Published Oct 21, 2026 · Updated 20 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 3 in a dayToday
CVSS5.4Medium · v3.1
EPSS0.21%12th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Splunk
IdentifiersCVE-2026-76287CWE-639 · Authorization Bypass Through…

CVE-2026-76287 is an ownership authorization vulnerability in the Splunk Enterprise Data Management REST API affecting versions below 10.4.4. The API checks whether a requester has the preview_data_management_pipeline or edit_data_management_pipeline_job capability but does not verify ownership of the requested Data Management SPL2 preview job. Consequently, an authenticated user with either capability can read or delete preview jobs and results belonging to other users. The affected API is available only when Edge Processor is enabled, which is disabled by default.

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.

Exploitation can disclose data contained in other users' SPL2 preview jobs and results and permit unauthorized deletion of those resources, disrupting affected users' data-transformation preview workflows. The vulnerability has a reported CVSS v3 score of 5.4.

Mitigation

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

If immediate upgrading is not possible, disable Edge Processor where operationally feasible to make the affected REST API unavailable. Alternatively, remove the preview_data_management_pipeline and edit_data_management_pipeline_job capabilities from untrusted or unnecessary roles. These measures reduce exposure based on the exploitation prerequisites; they are not explicitly prescribed vendor workarounds. Review operational dependencies before disabling the feature.

Remediation

Patch, then assume compromise.

Upgrade Splunk Enterprise to version 10.4.4 or a later fixed release.

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-2026-76287 exploited in the wild?
As of Oct 30, 2026, Mallory has no reports of CVE-2026-76287 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76287?
As of Oct 30, 2026, Mallory has found no public exploit for CVE-2026-76287.
Is there a patch for CVE-2026-76287?
Upgrade Splunk Enterprise to version 10.4.4 or a later fixed release.
What products are affected by CVE-2026-76287?
Splunk.
How severe is CVE-2026-76287?
CVE-2026-76287 has a CVSS v3.1 score of 5.4 (Medium) and an EPSS score of 0.21% (12th percentile) as of Oct 30, 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.