CVE-2026-131300: Sensitive Information Disclosure through the REST API in Splunk App for Stream

Published Nov 19, 2026
·
Updated

In Splunk App for Stream versions below 8.1.7, a user who can read splunkdaccess.log or the internal Splunk index could recover the Stream forwarder authentication key and use it to impersonate a trusted Stream forwarder. The vulnerability is possible because Splunk App for Stream sends the authentication key in an internal request URL, and Splunk records that URL in splunkdaccess.log. For more information see About Splunk Stream (https://help.splunk.com/en/splunk-enterprise/collect-stream-data/install-and-configure-splunk-stream/8.1/introduction/about-splunk-stream) and restmap.conf (https://help.splunk.com/en/splunk-enterprise/administer/admin-manual/9.4/configuration-file-reference/9.4.3-configuration-file-reference/restmap.conf) in the Splunk documentation.

Affected Software

1 affected component
Splunk Splunk App for Stream<8.1.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.1.7

Event History

Nov 19, 2026
CVE Published
via MITRE·07:56 PM
Data Sourced
via MITRE·07:56 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who is realistically exposed to this issue?

Splunk App for Stream deployments below 8.1.7 are exposed if a user can read splunkd_access.log or search the _internal Splunk index. The impact is limited to recovery of the Stream forwarder authentication key from recorded internal request URLs.

2

What does an attacker need to exploit it?

An attacker needs access that allows them to read splunkd_access.log or the _internal index. They do not need user interaction, but they must be able to obtain the logged internal request URL containing the authentication key.

3

What can an attacker do with the recovered key?

The recovered Stream forwarder authentication key can be used to impersonate a trusted Stream forwarder.

4

What can be done if upgrading is not immediately possible?

Restrict access to splunkd_access.log and to the _internal Splunk index to reduce the chance that users can recover the authentication key. Review which users currently have access to these sources.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203