# CVE-2026-76268: Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise

> Unauthenticated attackers can execute arbitrary OS commands via the Patroni REST API in Splunk Enterprise search head clusters.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-rxjh-rj2v-47gx

## What is CVE-2026-76268?

CVE-2026-76268 is a critical missing authorization vulnerability in Splunk Splunk, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Splunk Enterprise versions below 10.4.3 and 10.2.7, an unauthenticated user with network access to the Patroni Representational State Transfer (REST) Application Programming Interface (API) on a search head cluster member could execute attacker-controlled operating-system commands. The vulnerability is possible because this interface does not require authentication for critical configuration operations. For more information see Sidecar configuration settings (https://help.splunk.com/en/data-management/splunk-enterprise-admin-manual/10.2/splunk-sidecars/sidecar-configuration-settings) in the Splunk documentation.

Splunk Enterprise versions 10.0.x and 9.4.x are not affected.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Splunk Splunk.

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

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

## Is CVE-2026-76268 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76268 exists.

Public exploit code:

- CVE-2026-76268 PoC: Splunk Enterprise SHC Patroni REST unauth RCE — PATCH /config archive_command + POST /restart. Check + mass exploit, OOB POCBIT-76268-OK, CVSS 9.8. https://pocbit.org/pocs/cve-2026-76268 (github_poc): https://github.com/murrez/CVE-2026-76268
- Splunk Enterprise Patroni REST API - Missing Authentication RCE (nuclei): http/cves/2026/CVE-2026-76268.yaml

## Other vulnerabilities in Splunk Splunk

- [CVE-2026-20253](https://insights.sbomify.com/CVE-2026-20253/): Splunk Enterprise Missing Authentication for Critical Function (critical 9.8, exploited in the wild)
- [CVE-2026-76284](https://insights.sbomify.com/CVE-2026-76284/): Improper Neutralization in Splunk Enterprise (critical 9.8)
- [CVE-2026-76285](https://insights.sbomify.com/CVE-2026-76285/): Improper Adherence to Coding Standards in Splunk Enterprise (critical 9.8)
- [CVE-2017-17067](https://insights.sbomify.com/CVE-2017-17067/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-10126](https://insights.sbomify.com/CVE-2016-10126/): Information disclosure in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76268 is a critical missing authorization vulnerability in Splunk Splunk, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76268 exists.

Affected product: Splunk Splunk. 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-76268/ (Markdown: https://insights.sbomify.com/CVE-2026-76268/index.md)
```

## Sources

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

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