CVE-2026-76257: In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions bel

Routine

MEDIUM 6.5UPGRADEUPGRADE

CVE-2026-76257 is a medium-severity flaw (CVSS 6.5) affecting splunk, splunk secure gateway. 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, and Splunk Secure Gateway versions below 3.10.10, 3.9.24, and 3.8.71, a user who holds a Splunk role with permissions to list storage passwords but does not hold Splunk Secure Gateway administration privileges could access Mobile Device Management signing secrets that compromise all affected mobile-device enrollment trust through Splunk Secure Gateway. The vulnerability is po

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 73%)
CISA exploited list	No
Weakness	CWE-862
Published	2026-08-19
Last modified	2026-10-26

Publisher (CNA): Cisco Systems, Inc. · Vendor: splunk

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-08-19 22:17 UTCPublished CVE record published
2026-10-26 10:10 UTCUpdated 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.

splunk splunk secure gateway UPGRADE

Affected: >= 3.8.0 and < 3.8.71 · >= 3.9.0 and < 3.9.24 · >= 3.10.0 and < 3.10.10

Fixed in: 3.8.71, 3.9.24, 3.10.10

Safe to downgrade to: a release before 3.8.0

1. Check installed version

apt-cache policy splunk-secure-gateway || rpm -q splunk-secure-gateway || splunk-secure-gateway --version

2. UPGRADE to 3.8.71 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade splunk-secure-gateway

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade splunk-secure-gateway

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 3.8.0 (Debian / Ubuntu)

apt-cache madison splunk-secure-gateway sudo apt install splunk-secure-gateway=<VERSION_BEFORE_3.8.0> sudo apt-mark hold splunk-secure-gateway

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list splunk-secure-gateway sudo dnf downgrade splunk-secure-gateway-<VERSION_BEFORE_3.8.0> sudo dnf versionlock add splunk-secure-gateway

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.

Quick answers

How do I fix CVE-2026-76257?

splunk: upgrade to 9.4.14, 10.0.9, 10.2.6, 10.4.2; splunk secure gateway: upgrade to 3.8.71, 3.9.24, 3.10.10. Exact commands for each OS are on this page.

Is CVE-2026-76257 being exploited?

CVE-2026-76257 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-76257 affect?

CVE-2026-76257 affects splunk, splunk secure gateway. Severity is medium (CVSS 6.5). In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below 3.10.10, 3.9.24, and 3.8.71, a user who holds a Splunk role with permissions to list storage passwords but does not hold Splunk

How urgent is CVE-2026-76257?

Priority 30/100. No elevated risk signals yet.

Software pages

Splunk vulnerabilities

Related CVEs

CVE-2026-76258 MEDIUM 6.5 UPGRADE UPGRADE In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions bel
CVE-2026-76261 MEDIUM 5.3 UPGRADE UPGRADE In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions bel
CVE-2026-76256 MEDIUM 4.3 UPGRADE UPGRADE In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions bel
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
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

References

← Back to latest CVEs