PatchTheCVECVE-2026-76311: 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
50
This month
CRITICAL 9.4REMOTEUPGRADE
CVE-2026-76311 is a critical-severity flaw (CVSS 9.4) affecting splunk. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, an unauthenticated user who has an embedded report token could download the dispatch archive for an embedded report search job and use exposed session material to access all relevant data and affect system integrity on the Splunk platform instance. The vulnerability is possible because the embedded report authorization flow does not block dispatch archive download requests be
Why this priority
- Critical severity
- CISA SSVC: automatable with total technical impact
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.4 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.4% (top 62%) |
| CISA exploited list | No |
| Weakness | CWE-284 |
| 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.4.0 and < 9.4.14 · >= 10.0.0 and < 10.0.9 · >= 10.2.0 and < 10.2.6 · >= 10.4.0 and < 10.4.2
Fixed in: 9.4.14, 10.0.9, 10.2.6, 10.4.2
Safe to downgrade to: a release before 9.4.0
1. Check installed version
apt-cache policy splunk || rpm -q splunk || splunk --version
2. UPGRADE to 9.4.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.4.0 (Debian / Ubuntu)
apt-cache madison splunk
sudo apt install splunk=<VERSION_BEFORE_9.4.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.4.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.
Exact fixes by distribution
Fedora 46 · python-trimesh · FIXED · 5.2.0-1.fc46 · FEDORA-2026-429b4bad4c · source
sudo dnf upgrade --advisory=FEDORA-2026-429b4bad4c
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-76259 HIGH 8.8 UPGRADE 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