Skip to main content
VulnerabilityPublished

CVE-2026-76267: Splunk Enterprise · The software does not neutralize or incorrectly neutralizes output that is written to logs.

Affects Splunk EnterpriseSource CVE Database V5

0
Compare

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

Data as of 21 Nov 2026, 17:35 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 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 21 Nov 2026.

What to do

Upgrade Splunk Enterprise to 10.4.3, 10.2.7 or 10.0.10.

Affected software

ProductAffectedFixed in
SplunkSplunk EnterpriseAffected
  • >=10.4 <10.4.3
Fixed in
  • 10.4.3
SplunkSplunk EnterpriseAffected
  • >=10.2 <10.2.7
Fixed in
  • 10.2.7
SplunkSplunk EnterpriseAffected
  • >=10.0 <10.0.10
Fixed in
  • 10.0.10

AI-suggested

A fix is available in Splunk Enterprise versions 10.4.3, 10.2.7, and 10.0.10. Users should upgrade to these or later versions to remediate the vulnerability. No additional mitigation guidance is provided or necessary beyond applying the official patches.

Description

CVE-2026-76267 is a vulnerability in Splunk Enterprise that affects versions prior to 10.4.3, 10.2.7, and 10.0.10. It allows users with the read_o11y_content capability to inject forged log entries via the REST API because the Splunk App for Splunk O11y Cloud does not properly neutralize user-supplied SignalFlow content before logging. Versions 9.4.x are not affected.

References

Community reviews

Loading reviews…