In Splunk App for Stream versions below 8.1.7, an unauthenticated user could cause Splunk App for Stream to reset its in-memory indexer cache.
The vulnerability exists because the Splunk Web handler accepts the cache-reset request without requiring a login.
For more information see Splunk Stream installation package overview (https://help.splunk.com/en/data-management/collect-stream-data/install-and-configure-splunk-stream/8.0/introduction/splunk-stream-installation-package-overview) and Launch Splunk Web (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/10.6/administer-splunk-enterprise-with-splunk-web/launch-splunk-web) in the Splunk documentation.
Show the promptExplain CVE-2026-131301 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-131301?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-131301?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-131301 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.