CVE-2026-76267 Log Injection through the REST API in Splunk App for Splunk O11y Cloud
A user with read_o11y_content capability can inject forged entries into the app log via the REST API in Splunk Enterprise.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-76267?
CVE-2026-76267 is a medium-severity vulnerability in Splunk Splunk, published on 7 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-117
Which versions are affected by CVE-2026-76267?
It affects 1 product.
Products include Splunk Splunk.
How do I fix CVE-2026-76267?
No fix has been published for CVE-2026-76267 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-76267 being exploited?
There is no known exploitation of CVE-2026-76267 in the wild and no public exploit code.
Other vulnerabilities in Splunk Splunk
- CVE-2026-20253 Splunk Enterprise Missing Authentication for Critical Function
- CVE-2026-76268 Missing Authentication for Critical Function in the Patroni REST API in Splunk Enterprise
- CVE-2026-76284 Improper Neutralization in Splunk Enterprise
- CVE-2026-76285 Improper Adherence to Coding Standards in Splunk Enterprise
- CVE-2017-17067 Auth bypass in n/a
Sources
Also known as GHSA-xv3j-9ggm-62xg.