CVE-2026-76267

Log Injection through the REST API in Splunk App for Splunk O11y Cloud

Published Oct 7, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

A flaw in the Splunk App for Splunk O11y Cloud allows a user with read_o11y_content capability to insert forged entries into the application log via the REST API. This is an instance of log injection (CWE-117), where user‑supplied data is written to log output without proper sanitization. The main consequence is that attackers can alter log contents, potentially hiding malicious activity or fabricating malicious events, which undermines incident response and forensic accuracy.

Affected Systems

Splunk Enterprise versions earlier than 10.4.3, 10.2.7, and 10.0.10 are affected. The 9.4.x series is not impacted. Any deployment that uses the Splunk App for Splunk O11y Cloud and assigns users the read_o11y_content role can be targeted.

Risk and Exploitability

The CVSS score of 4.3 indicates moderate severity. EPSS is not available, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a user possessing the read_o11y_content role gaining access to the REST API of the app; the attacker can craft requests that inject arbitrary log entries. Given the absence of a publicly known exploit and the requirement for specific role permissions, the risk of widespread exploitation remains low, but the potential impact on log integrity warrants attention.

Remediation

Vendor Solution

Upgrade Splunk Enterprise to versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15, or higher.


Vendor Workaround

Turn off or remove the Splunk App for Splunk O11y Cloud. For more information see [Manage app and add-on objects](https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.2/meet-splunk-apps/manage-app-and-add-on-objects) in the Splunk documentation.


OpenCVE Recommended Actions

  • Upgrade Splunk Enterprise to any of the supported versions 10.4.3, 10.2.7, or 10.0.10 or later.
  • Turn off or remove the Splunk App for Splunk O11y Cloud if upgrade is not immediately possible.
  • Revoke the read_o11y_content role from users who do not require it to reduce the attack surface.

Generated by OpenCVE AI on October 7, 2026 at 23:31 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Splunk splunk
CPEs cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*
Vendors & Products Splunk splunk
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Splunk
Splunk splunk Enterprise
Vendors & Products Splunk
Splunk splunk Enterprise
Type Values Removed Values Added
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.
Title Log Injection through the REST API in Splunk App for Splunk O11y Cloud
Weaknesses CWE-117
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses
  • CWE-117

    Improper Output Neutralization for Logs

Sources

Status
PUBLISHED
Assigner
cisco
Published
Updated
Oct 8, 2026, 3:09 PM
Reserved
Aug 19, 2026, 12:02 PM
Status
Analyzed
Published
Oct 7, 2026, 9:17 PM
Modified
Oct 14, 2026, 12:21 PM