Skip to main content
VulnerabilityPublished

CVE-2026-76261: 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.9, 3.9.23, and 3.8.70, a user

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76261· Medium 5.3

Not known to be exploited · CVSS 5.3 Medium · fixed in 10.4.2 : update Splunk Enterprise when convenient.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 10.4.2, 10.2.6, 10.0.9 +4
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Splunk to 10.4.2, 10.2.6, 10.0.9 or 9.4.14 (Enterprise); 3.10.9, 3.9.23 or 3.8.70 (Secure Gateway).

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.4 <10.4.2
Fixed in
  • 10.4.2
SplunkSplunk EnterpriseAffected
  • >=10.2 <10.2.6
Fixed in
  • 10.2.6
SplunkSplunk EnterpriseAffected
  • >=10.0 <10.0.9
Fixed in
  • 10.0.9
SplunkSplunk EnterpriseAffected
  • >=9.4 <9.4.14
Fixed in
  • 9.4.14
SplunkSplunk Secure GatewayAffected
  • >=3.10 <3.10.9
Fixed in
  • 3.10.9
SplunkSplunk Secure GatewayAffected
  • >=3.9 <3.9.23
Fixed in
  • 3.9.23

AI-suggested

Mitigation involves ensuring that private-key migration is complete after upgrading from older Splunk Secure Gateway deployments to prevent key material from remaining accessible with insecure default access controls. Restricting access to the Key Value Store REST API and verifying role permissions may reduce exposure until an official fix is applied.

Description

A vulnerability in Splunk Enterprise and Splunk Secure Gateway allows users without admin or power roles to read Spacebridge asymmetric private keys via the Splunk Secure Gateway App Key Value Store REST API. This occurs on instances upgraded from older deployments where private-key migration is incomplete, leaving key material accessible due to insecure default access controls. The issue affects versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14 for Splunk Enterprise, and below 3.10.9, 3.9.23, and 3.8.70 for Splunk Secure Gateway. The vulnerability has a CVSS score of 5.3 (medium severity).

References

Community reviews

Loading reviews…