Live › vulnerability › CVE-2026-76288
Go to dashboardAn unauthenticated attacker can send a single crafted request to the Splunk Web JavaScript logger endpoint, which stops Splunk Web from answering requests. Splunk Web stays down until Splunk Enterprise is restarted, because request-header parsing has no size limit.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Any Splunk Enterprise deployment below the fixed versions that serves Splunk Web is exposed, and an unauthenticated request is enough to trigger the outage. Splunk Cloud, Universal Forwarders and deployments with Splunk Web disabled are not described as affected by the sources.
No product ranges from the sources yet.
$SPLUNK_HOME/bin/splunk version and compare it with the fixed releases below.8000 from the internet.10.4.4, 10.2.8, 10.0.11, or 9.4.16, matching your release line.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
In Splunk Enterprise versions below 10.4.4, 10.2.8, 10.0.11, and 9.4.16, an unauthenticated user could send a single crafted request to the Splunk Web JavaScript logger endpoint and cause Splunk Web to stop responding to requests. Splunk Web remains unavailable until Splunk Enterprise is restarted. The vulnerability is possible because Splunk Web does not limit request-header parsing before processing the request.
This page as .md · .json · in your agent: get_signal("CVE-2026-76288")
NVD data is provided by NIST and is public domain · EPSS scores by FIRST, used with attribution. Posts quoted belong to their authors.