Skip to main content
CVE-2026-76347VulnerabilityPublished

In Splunk Enterprise versions below 10.4.2, 10.2.6, 10.0.9, and 9.4.14, and Splunk Secure Gateway versions below

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76347· Medium 5.4

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

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.4Medium
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:L/PR:L/UI:N/S:U/C:N/I:L/A:L

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 18 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

If you cannot patch yet, restrict user roles to prevent unauthorized users from sending report notifications or accessing vulnerable versions.

Description

A Server-Side Request Forgery (SSRF) vulnerability exists 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. This vulnerability allows users without admin or power roles to send system-authenticated requests to internal Splunk services via report notifications. Exploitation could lead to unauthorized changes to Search Head Cluster state and denial of service. The issue arises because Splunk Secure Gateway does not validate report notification path values before sending internal requests.

References

Community reviews

Loading reviews…