Skip to main content

CVE-2026-76296: The software does not perform an authorization check when an actor attempts to access a resource or perform an action. in Splunk Splunk Enterprise

0
Medium
VulnerabilityCVE-2026-76296cvecve-2026-76296
Published: 10/21/2026 (10/21/2026, 22:51:58 UTC)
Source: CVE Database V5
Vendor/Project: Splunk
Product: Splunk Enterprise

Description

CVE-2026-76296 is a vulnerability in Splunk Enterprise versions prior to 10.4.4, 10.2.8, 10.0.11, and 9.4.16 where unauthorized users with roles other than 'admin' or 'power' can create, move, edit, or delete sourcetype renaming configurations in apps they do not have permission to access. This occurs because Splunk Web does not perform proper authorization checks before allowing sourcetype renaming operations.

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.4>=10.2 <10.2.8>=10.0 <10.0.11>=9.4 <9.4.16

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/21/2026, 23:15:59 UTC

Technical Analysis

In affected versions of Splunk Enterprise, the software fails to verify app permissions when users attempt to perform sourcetype renaming operations via Splunk Web. This lack of authorization checks allows users without 'admin' or 'power' roles to manipulate sourcetype renaming configurations in apps they should not access. The issue arises specifically when Splunk Web is enabled, as it does not enforce the required app permissions for these operations.

Potential Impact

The vulnerability allows users with limited privileges (non-admin, non-power roles) to modify sourcetype renaming configurations in unauthorized apps. This can lead to integrity issues where sourcetype data is incorrectly renamed, potentially affecting data processing and search results. There is no direct confidentiality or availability impact reported.

Mitigation Recommendations

A fix is available in Splunk Enterprise versions 10.4.4, 10.2.8, 10.0.11, and 9.4.16. Users should upgrade to these or later versions to remediate the vulnerability. Until patched, restricting access to Splunk Web or limiting user roles to trusted users may reduce exposure.

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.622Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ad944324d27ba8daa0bcbb8

Added to database: 10/21/2026, 23:01:06 UTC

Last enriched: 10/21/2026, 23:15:59 UTC

Last updated: 10/21/2026, 23:15:59 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