What is CVE-2026-76267?
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.
The record classifies CVE-2026-76267 under weakness class CWE-117. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 3 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 4.3 — MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N - EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 5.3% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 2.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-10-07, last modified 2026-10-08
Is CVE-2026-76267 being exploited?
It currently carries a trending score of 36 in the Threadlinqs vulnerability feed.
Affected products and versions
- Splunk: Enterprise
How to fix CVE-2026-76267
No vendor patch reference has been recorded for CVE-2026-76267 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-76267
1 tracked threat in the Threadlinqs corpus references CVE-2026-76267, either in the campaign’s CVE list or as an indicator on the campaign record.
Sources
Enriched from CVE.org, FIRST EPSS. Last verified by Threadlinqs on .