Splunk App for Stream auth key in REST API logs enables forwarder impersonation
- Exploited
- No known exploitation
- Fix
- Fixed in 8.1.7
- Who is exposed
- Not reported
Summary
In Splunk App for Stream versions below 8.1.7, a user who can read splunkd_access.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 splunkd_access.log. For more information see About Splunk Stream (help.splunk.com/
What to do
Upgrade to a fixed version: 8.1.7.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131300 (Sensitive Information Disclosure through the REST API in Splunk App for Stream), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131300 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk App for Stream: fixed in 8.1.7
Fixed versions: 8.1.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131300 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131300 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://advisory.splunk.com/advisories/SVD-2026-1110
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131300
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131300"}.Affected versions
- Splunk Splunk App for Streamfixed in 8.1.7
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1110 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131300 |
| Record | NVD · CVE-2026-131300 |
Questions about CVE-2026-131300
Is CVE-2026-131300 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-131300?
Splunk App for Stream: before 8.1.7.
Source: cve.now feed data
How do I fix CVE-2026-131300?
Upgrade to a fixed version: 8.1.7.
Source: cve.now feed data
Related
- CVE-2023-32713Local Privilege Escalation via the ‘streamfwd’ program in Splunk App for Stream
- CVE-2026-131299Extensible Markup Language External Entity Injection through the REST API in Splunk App for Stream
- CVE-2026-131301Missing Authorization through Splunk Web in Splunk App for Stream
- CVE-2026-131287Remote Code Execution (RCE) through the REST API in Splunk SOAR
- CVE-2026-131295Improper Authorization in Playbook Execution in Splunk SOAR
- CVE-2026-131293Improper Access Control in the Data Management Automation API in Splunk SOAR
No corrections so far. Something wrong on this page? Report an error.