CVE-2026-76533 in Splunkinfo

Summary

by MITRE • 11/20/2026

In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 on Ubuntu and AlmaLinux, an unauthenticated user who obtains a valid Splunk Web session cookie before the affected user logs out could continue using the cookie after logout to access data and perform actions available to that user. The vulnerability is possible because the logout flow does not invalidate the associated session token on affected deployments. The attacker must obtain the valid session cookie before the affected user logs out of Splunk Web. The issue was reproduced in Splunk Enterprise installations on Ubuntu and AlmaLinux.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Analysis

by VulDB Data Team • 11/20/2026

The identified vulnerability represents a critical failure in session management within specific versions of Splunk Enterprise, specifically those running below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 on Ubuntu and AlmaLinux operating systems. This flaw allows an unauthenticated attacker to maintain access to the application using a session cookie that should have been invalidated upon user logout. The core technical deficiency lies in the authentication mechanism's inability to properly terminate active sessions when a legitimate user initiates a logout sequence. Instead of revoking the associated session token on the server side, the system continues to accept and validate the existing cookie for subsequent requests. This behavior creates a window of opportunity where previously valid credentials remain functional indefinitely or until their natural expiration time elapses, bypassing standard security controls designed to restrict access after user disengagement.

From an operational perspective, this vulnerability enables unauthorized data exfiltration and potential system compromise if the compromised account possesses administrative privileges. An attacker who obtains a valid Splunk Web session cookie prior to the target user logging out can continue to interact with the platform as that authenticated user. This includes viewing sensitive logs, executing search queries against confidential datasets, and potentially performing configuration changes depending on the role assigned to the affected account. The attack vector requires initial access to capture the session token, which could be achieved through network sniffing if transport layer security is misconfigured, cross-site scripting attacks targeting users with active sessions, or physical theft of an unattended workstation where a user has not yet logged out. Once captured, the cookie can be replayed by the attacker in their own browser to impersonate the legitimate user without needing additional authentication factors such as passwords or multi-factor authentication tokens.

This issue aligns closely with CWE-613, which describes insufficient session expiration, and more specifically reflects aspects of CWE-384 regarding Session Fixation if an attacker can force a victim to use a known session ID, though the primary mechanism here is the failure to invalidate sessions upon logout rather than fixation during login. In terms of the MITRE ATT&CK framework, this vulnerability facilitates lateral movement and credential access techniques, particularly T1078 Valid Accounts where attackers leverage legitimate credentials or tokens to maintain persistence within an environment. The lack of server-side session invalidation means that even if a user believes they have secured their account by logging out, the underlying security context remains active and exploitable by any party in possession of the captured cookie data.

Mitigation strategies must prioritize immediate patching to versions 10.4.5, 10.2.9, 10.0.12, or 9.4.17 and later for Ubuntu and AlmaLinux deployments where these vulnerabilities are present. For organizations unable to immediately apply patches due to operational constraints, implementing compensating controls is essential. These include enforcing strict transport layer security policies such as HTTPS with HSTS to prevent cookie interception via network sniffing. Additionally, configuring shorter session timeout durations can reduce the window of opportunity for attackers to exploit captured cookies before they expire naturally. Enabling multi-factor authentication adds a secondary verification step that may mitigate some risks if the attacker only possesses the static session token but not the second factor. Regular auditing of active sessions and monitoring for anomalous login patterns from unusual IP addresses or geographic locations can also help detect unauthorized usage of these lingering tokens.

Responsible

Cisco

Reservation

08/19/2026

Disclosure

11/20/2026

Moderation

accepted

CPE

ready

EPSS

0.00178

KEV

no

Activities

very low

Sources

Do you want to use VulDB in your project?

Use the official API to access entries easily!