Skip to main content

CVE-2026-76273: The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program. in Splunk Splunk Enterprise

0
Medium
VulnerabilityCVE-2026-76273cvecve-2026-76273
Published: 10/07/2026 (10/07/2026, 20:46:33 UTC)
Source: CVE Database V5
Vendor/Project: Splunk
Product: Splunk Enterprise

Description

CVE-2026-76273 is a medium severity vulnerability in Splunk Enterprise versions prior to 10.4.3, 10.2.7, 10.0.10, and 9.4.15. It allows users with the run_collect capability to use the collect SPL command to inject attacker-controlled content into system-level messages due to improper validation of the index name. This could affect the integrity of system messages but does not impact confidentiality or availability.

CVSS v3.1

Score 4.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected software

Splunk

Splunk Enterprise

Affected versions
>=10.4 <10.4.3>=10.2 <10.2.7>=10.0 <10.0.10>=9.4 <9.4.15

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/07/2026, 21:19:44 UTC

Technical Analysis

In affected versions of Splunk Enterprise, the collect Search Processing Language (SPL) command does not properly validate the index name parameter before processing it. A user with the run_collect capability can exploit this to insert arbitrary content into system-level messages on the Splunk platform instance. This vulnerability arises from insufficient input validation affecting control or data flow within the program.

Potential Impact

The vulnerability allows an attacker with run_collect capability to add attacker-controlled content to system-level messages, potentially misleading administrators or affecting system monitoring. There is no impact on confidentiality or availability reported. The CVSS score is 4.3 (medium), reflecting limited impact primarily on integrity.

Mitigation Recommendations

A fix is available in Splunk Enterprise versions 10.4.3, 10.2.7, 10.0.10, and 9.4.15. Users should upgrade to these or later versions to remediate the vulnerability. No other mitigation steps are indicated by the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
cisco
Date Reserved
2026-08-19T12:02:03.620Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ac6b3c92cdf04f6567ed5cc

Added to database: 10/07/2026, 21:04:09 UTC

Last enriched: 10/07/2026, 21:19:44 UTC

Last updated: 10/07/2026, 21:19:44 UTC

Views: 6

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses