Skip to main content
Menu
CVEs

Splunk App for Stream local file read via XXE in REST API vocabulary upload

CVE-2026-131299Published November 19, 2026, updated

7.5HighCNA
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, 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 (help.splunk.com/en/splunk-enterprise/collect-stream-data/install-and-configure-splunk-stream/8.1/introduction/about-splunk-stream) and restmap.conf (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.

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.

“In Splunk App for Stream versions below 8.1.7”

advisory.splunk.com

What to do

  1. Upgrade to a fixed version: 8.1.7.

  2. Workaround: Turn off or remove the Splunk App for Stream.

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-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"}.

Affected versions

cve.now Index

28Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 73 if added to CISA KEV
  • Would score about 68 if CISA's SSVC rates exploitation active
  • Would score about 33 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkadvisory.splunk.com · advisories/SVD-2026-1110
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-131299
RecordNVD · CVE-2026-131299

Questions about CVE-2026-131299

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: cve.now feed data

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: advisory.splunk.com, cve.org

Which versions are affected by CVE-2026-131299?

Splunk App for Stream: before 8.1.7.

Source: cve.now feed data

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: advisory.splunk.com, cve.org

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: cve.now feed data, cve.org

No corrections so far. Something wrong on this page? Report an error.