Skip to main content
Menu
CVEs

Splunk SOAR information disclosure of stored password in REST API

Splunk SOAR below 8.8.0 is affected where a user with the System Settings edit permission can make it send a stored Elasticsearch password to a host that user controls. Fixed in 8.8.0.

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

7.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 8.8.0
Who is exposed
Specific setups only

Summary

Written by a model

In Splunk SOAR versions below 8.8.0, a user that holds a role with the System Settings edit permission could cause Splunk SOAR to send a stored Elasticsearch password to a host that the user controls. The vulnerability is possible because Splunk SOAR reuses a stored Elasticsearch password for a changed Search Settings endpoint without requiring a replacement password.

Who should check

Teams running on-premises Splunk SOAR below 8.8.0 that have Elasticsearch search settings configured, and anyone granting System Settings edit permission.

“Splunk SOAR 8.8 Below 8.8.0 8.8.0”

advisory.splunk.com

What to do

  1. Check whether your setup matches what the bug needs.

    Splunk SOAR versions below 8.8.0 A user holding a role with the System Settings edit permission
  2. Upgrade to a fixed version: 8.8.0.

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-131266 (Information Disclosure through the REST API in Splunk SOAR), 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-131266 (entry last updated 2026-11-19):
Affected:
- Splunk Splunk SOAR: fixed in 8.8.0
Fixed versions: 8.8.0.
Conditions (all must be true for the bug to be hit):
- Splunk SOAR versions below 8.8.0 (source: https://advisory.splunk.com/advisories/SVD-2026-1108)
- A user holding a role with the System Settings edit permission (source: https://advisory.splunk.com/advisories/SVD-2026-1108)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-131266 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131266 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-1108
- https://www.cve.org/CVERecord?id=CVE-2026-131266
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-131266
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-131266"}.

Affected versions

cve.now Index

16Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.7/10CVSS 7.7
  • No patch0/5No signal

What would change the score

  • Would score about 66 if added to CISA KEV
  • Would score about 61 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 3

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

Questions about CVE-2026-131266

Is CVE-2026-131266 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?

A user with a role that holds the System Settings edit permission can make Splunk SOAR send a stored Elasticsearch password to a host that the user controls, which exposes that credential.

Source: advisory.splunk.com, cve.org

Which versions are affected by CVE-2026-131266?

Splunk SOAR: before 8.8.0.

Source: cve.now feed data

Am I affected, and how do I check?

Splunk SOAR versions below 8.8.0 are affected, in setups where users hold roles with the System Settings edit permission. To check, look at the installed Splunk SOAR version and review which roles include that permission.

Source: advisory.splunk.com, cve.org

How do I fix CVE-2026-131266?

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

Source: cve.now feed data, cve.org

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