CVE Watchtower

CVE-2026-76533Splunk Enterprise Insufficient Session Expiration

NVD

Vulnerability Summary

Improper Authentication Handling after Splunk Web Logout in Splunk Enterprise. 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.
Severity Level
MEDIUM(4.2)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
According to WASC, Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.
CVSS v3.1 Base Metrics — Score 4.2 (MEDIUM)
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

Affected & Patched Versions

Affected Versions
  • Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17 on Ubuntu and AlmaLinux
Patched Versions
  • Upgrade Splunk Enterprise versions 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.

What to do

Fix it during your normal patch cycle. No exploitation is confirmed yet.

  1. Check whether you run Splunk Enterprise and which version.
  2. Update to a patched version listed above, then confirm the new version.
  3. Until you can update, follow the vendor workaround: The vulnerability affects instances with Splunk Web turned on. Turning Splunk Web off is a possible workaround. See Disable unnecessary Splunk Enterprise components and the web.conf configuration specification file for more information on turning off Splunk Web.

Timeline

  • Nov 19, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Splunk Enterprise CVEsYou are reading CVE-2026-76533. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Splunk Enterprise CVEs

Data last checked: Nov 19, 2026 02:25 UTC