Skip to main content
EPSS 0.3%top 81%

CVE-2026-76263: The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. in Splunk Splunk Enterprise

0
Medium
VulnerabilityCVE-2026-76263cvecve-2026-76263
Published: 08/19/2026 (08/19/2026, 21:34:19 UTC)
Source: CVE Database V5
Vendor/Project: Splunk
Product: Splunk Enterprise

Description

CVE-2026-76263 is a medium severity vulnerability in Splunk Enterprise that affects versions 10.2 up to but not including 10.2.6 and versions 10.4 up to but not including 10.4.2. It allows users without admin or power roles to delete SPL2 modules owned by other users due to broken object-level authorization in the data management orchestrator interface. The vulnerability arises because the system does not verify ownership before allowing deletion of these modules.

CVSS v3.1

Score 5.4medium

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

Affected software

Splunk

Splunk Enterprise

Affected versions
>=10.4 <10.4.2>=10.2 <10.2.6

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/11/2026, 07:18:31 UTC

Technical Analysis

In Splunk Enterprise versions >=10.2 <10.2.6 and >=10.4 <10.4.2, a user lacking admin or power roles can delete SPL2 modules belonging to other users via the data management orchestrator interface. This occurs because the authorization mechanism does not confirm that the requesting user owns the target resource before permitting deletion, resulting in broken object-level authorization. Versions below 10.2 are not affected.

Potential Impact

An unauthorized user with limited privileges can delete SPL2 modules owned by other users, potentially disrupting data processing or application functionality. The vulnerability does not allow data confidentiality compromise but impacts integrity and availability of user modules.

Mitigation Recommendations

Upgrade Splunk Enterprise to version 10.2.6 or later if using the 10.2 branch, or to version 10.4.2 or later if using the 10.4 branch, where this authorization issue is fixed. No other mitigations are indicated. Patch status is confirmed by the version ranges provided.

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: 6a862251acd9273b49a6fd9f

Added to database: 08/19/2026, 21:38:25 UTC

Last enriched: 09/11/2026, 07:18:31 UTC

Last updated: 10/04/2026, 10:04:22 UTC

Views: 41

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