CVE-2026-76259: In Splunk Enterprise for Windows versions below 10.4.2, 10.2.6, 10.0.9, 9.4.13, and 9.3.14, a local user with
32
Routine
HIGH 8.8UPGRADE
CVE-2026-76259 is a high-severity flaw (CVSS 8.8) affecting splunk. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
In Splunk Enterprise for Windows versions below 10.4.2, 10.2.6, 10.0.9, 9.4.13, and 9.3.14, a local user with access to the Windows host could bind to the management port before Splunk Enterprise starts, intercept authentication tokens from child processes, and use those tokens to compromise all relevant data and system integrity available to the user account running Splunk Enterprise. The vulnerability is possible because the Windows management-
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.8 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 94%) |
| CISA exploited list | No |
| Weakness | CWE-269 |
| Published | 2026-08-19 |
| Last modified | 2026-10-23 |
Publisher (CNA): Cisco Systems, Inc. · Vendor: splunk
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
splunk splunk UPGRADE
Affected: >= 9.3.0 and < 9.3.14 · >= 9.4.0 and < 9.4.13 · >= 10.0.0 and < 10.0.9 · >= 10.2.0 and < 10.2.6 · >= 10.4.0 and < 10.4.2
Fixed in: 9.3.14, 9.4.13, 10.0.9, 10.2.6, 10.4.2
Safe to downgrade to: a release before 9.3.0
1. Check installed version
apt-cache policy splunk || rpm -q splunk || splunk --version
2. UPGRADE to 9.3.14 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade splunk
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade splunk
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 9.3.0 (Debian / Ubuntu)
apt-cache madison splunk
sudo apt install splunk=<VERSION_BEFORE_9.3.0>
sudo apt-mark hold splunk
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list splunk
sudo dnf downgrade splunk-<VERSION_BEFORE_9.3.0>
sudo dnf versionlock add splunk
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Related CVEs
- CVE-2026-76311 CRITICAL 9.4 UPGRADE In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an emb