# CVE-2026-76290: Denial of Service (DoS) through Unauthenticated Package Downloads over the REST API in Splunk Enterprise


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-xj2g-87r9-g689

## What is CVE-2026-76290?

CVE-2026-76290 is a high-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026. 

### Official description

In Splunk Enterprise versions below 10.4.4, 10.2.8, and 10.0.11, an unauthenticated user could send repeated requests to the Edge Processor package download endpoint in the Splunk Pipeline Builders app. The requests could cause the Splunk daemon to consume excessive system resources and potentially stop responding.
The vulnerability is possible because the endpoint accepts package download requests without authentication and reads and base64-encodes the complete package in memory for each request.
After upgrading, prepare all existing Edge Processor instances, turn on authentication for Edge Processor package downloads, and restart Splunk Enterprise. For more information, see Enable authentication for Edge Processor package downloads (https://help.splunk.com/en/data-management/process-data-at-the-edge/use-edge-processors-for-splunk-enterprise/10.4/administer-edge-processors/enable-authentication-for-edge-processor-package-downloads).

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-76290?


## How do I fix CVE-2026-76290?

No fix has been published for CVE-2026-76290 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-76290 being exploited?

There is no known exploitation of CVE-2026-76290 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-76290 and fix it if it is affected.

What it is: CVE-2026-76290 is a high-severity vulnerability in Splunk Enterprise, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-76290 in the wild and no public exploit code.

Affected product: Splunk Enterprise. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-76290/ (Markdown: https://insights.sbomify.com/CVE-2026-76290/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-76290
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-76290
- OSV: https://osv.dev/vulnerability/CVE-2026-76290

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-76290/
Summaries are generated and may contain mistakes; the official description above is the record.