Medium [CVE-2026-76267] Log Injection through the REST API in Splunk App for Splunk O11y Cloud
This medium-severity Splunk advisory covers CVE-2026-76267 affecting Splunk Enterprise.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published
Android app · Google Play
Monitor future Splunk CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
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.
- Splunk Enterprise 10.4 before 10.4.3
- Splunk Enterprise 10.2 before 10.2.7
- Splunk Enterprise 10.0 before 10.0.10
Official advisory · high-confidence parse· fetched 1 day ago·verify at source
- 10.4.3
- 10.2.7
- 10.0.10
Official advisory · high-confidence parse· fetched 1 day ago·verify at source
Mitigation
Upgrade to a fixed release: 10.4.3, 10.2.7, 10.0.10. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 1 day ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.