Medium severity · published Oct 7, 2026
CVE-2026-76267
Log Injection through the REST API in Splunk App for Splunk O11y Cloud
4.3
CVSS
0.2%
EPSS
No
On KEV
Description
In Splunk Enterprise versions below 10.4.3, 10.2.7, and 10.0.10, a user that holds a role with the read_o11y_content capability could inject forged entries into the app log through the Representational State Transfer (REST) API. The vulnerability is possible because Splunk App for Splunk O11y Cloud does not neutralize user-supplied SignalFlow content before writing it to the app log.
Splunk Enterprise versions 9.4.x are not affected.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
None
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 13% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SE
Splunk Enterprise · Splunk
10.4 before 10.4.3; 10.2 before 10.2.7; 10.0 before 10.0.10 · source: vendor
SP
Splunk · Splunk
10.0.0 before 10.0.10; 10.2.0 before 10.2.7; 10.4.0 before 10.4.3 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-76267
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-76267
advisory.splunk.com
https://advisory.splunk.com/advisories/SVD-2026-1001
More from Splunk Enterprise
9.8
CVE-2026-20253
Unauthenticated Arbitrary File Creation and Truncation in a PostgreSQL Sidecar Service Endpoint in Splunk Enterprise
9.9
CVE-2026-76302
Security Hardening in Splunk Enterprise - October 2026
9.9
CVE-2026-76299
Security Hardening in Splunk Enterprise - October 2026
9.8
CVE-2026-76301
Security Hardening in Splunk Enterprise - October 2026
9.8
CVE-2026-76285
Improper Adherence to Coding Standards in Splunk Enterprise