CVE-2026-76285: Improper Adherence to Coding Standards in Splunk Enterprise

Q: Which Splunk Enterprise releases include the addressed fixes?

Splunk addressed the internally identified vulnerabilities in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15.

Q: Is this CVE tied to one specific underlying vulnerability?

No. The CVE represents a group of multiple internally identified vulnerabilities categorized under the same Common Weakness Enumeration (CWE).

Published Oct 7, 2026

Updated

As part of Cisco's ongoing commitment to proactive security and product quality, Cisco has conducted a comprehensive internal security review. This review resulted in a software hardening release that addresses multiple internally discovered vulnerabilities. The vulnerabilities tracked by CVE-2026-76285 are related to improper adherence to coding standards and are grouped under the Common Weakness Enumeration (CWE) CWE-710.

Affected Software

5 affected components

Splunk Splunk Enterprise=10.4.3, =10.2.7, =10.0.10, =9.4.15

Splunk splunk>=9.4.0<9.4.15

Splunk splunk>=10.0.0<10.0.10

Splunk splunk>=10.2.0<10.2.7

Splunk splunk>=10.4.0<10.4.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade Splunk Enterprise to a version that resolves this vulnerability.
Fixed in 10.4.3
Upgrade
Upgrade Splunk Enterprise to a version that resolves this vulnerability.
Fixed in 10.2.7
Upgrade
Upgrade Splunk Enterprise to a version that resolves this vulnerability.
Fixed in 10.0.10
Upgrade
Upgrade Splunk Enterprise to a version that resolves this vulnerability.
Fixed in 9.4.15

Event History

Oct 7, 2026

CVE Published

via MITRE·08:46 PM

Data Sourced

via MITRE·08:46 PM

RemedyDescriptionWeakness

Data Sourced

via NVD·09:17 PM

DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

Which Splunk Enterprise releases include the addressed fixes?

Splunk addressed the internally identified vulnerabilities in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15.

Is this CVE tied to one specific underlying vulnerability?