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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://advisory.splunk.com/advisories/SVD-2026-1001 Vendor Advisory, Mitigation
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 4.3 · splunkNVD modified 2026-10-14 12:21
Affected (CPE criteria) 1
cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
References 1
- https://advisory.splunk.com/advisories/SVD-2026-1001 Vendor Advisory, Mitigation