Skip to main content
Mallory
HighVulnerability

CVE-2026-76290: Unauthenticated denial of service in Splunk Enterprise Edge Processor package downloads

Published Oct 21, 2026 · Updated 19 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days6 mentions · peak 3 in a dayToday
CVSS7.5High · v3.1
EPSS0.50%43rd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Splunk
IdentifiersCVE-2026-76290CWE-400 · Uncontrolled Resource Consumption

CVE-2026-76290 is an unauthenticated resource-exhaustion vulnerability in the Edge Processor package download endpoint of the Splunk Pipeline Builders app in Splunk Enterprise. It affects releases below 10.4.4, 10.2.8, and 10.0.11 in the corresponding release branches. The endpoint accepts unauthenticated download requests and reads and base64-encodes the complete package in memory for each request. Repeated requests can consume excessive system resources and potentially make the Splunk daemon unresponsive. The vulnerability is rated CVSS v3 7.5.

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 can exhaust system resources and cause the Splunk daemon to stop responding, disrupting Splunk service availability and potentially interrupting dependent monitoring and investigation workflows.

Mitigation

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

If remediation must be delayed, consider disabling the Splunk Pipeline Builders app when unused, after reviewing dependencies and operational impact. Restrict network exposure of the affected download endpoint to trusted systems as an additional exposure-reduction measure.

Remediation

Patch, then assume compromise.

Upgrade Splunk Enterprise to 10.4.4, 10.2.8, or 10.0.11, or a later fixed release in the applicable branch. After upgrading, prepare all existing Edge Processor instances, enable authentication for Edge Processor package downloads, and restart Splunk Enterprise. The upgrade must be followed by these configuration steps.

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-76290 exploited in the wild?
As of Oct 30, 2026, Mallory has no reports of CVE-2026-76290 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-76290?
As of Oct 30, 2026, Mallory has found no public exploit for CVE-2026-76290.
Is there a patch for CVE-2026-76290?
Upgrade Splunk Enterprise to 10.4.4, 10.2.8, or 10.0.11, or a later fixed release in the applicable branch. After upgrading, prepare all existing Edge Processor instances, enable authentication for Edge Processor package downloads, and restart Splunk Enterprise.
What products are affected by CVE-2026-76290?
Splunk.
How severe is CVE-2026-76290?
CVE-2026-76290 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.50% (43rd percentile) as of Oct 30, 2026.
Activity feed

Recent activity

6 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.