Skip to main content
Menu
CVEs

Splunk SOAR information disclosure in REST API for approvals

Only affects Splunk SOAR versions below 8.8.0 for users holding permission to view an affected container. Fixed in 8.8.0.

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

7.6HighCNA
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, an authenticated user with permission to view an affected container could query the Representational State Transfer (REST) API for approvals to retrieve a live external prompt link belonging to another user. Using this link, the user could read the approval prompt without authentication and submit a response, potentially disrupting or altering the automated workflow governed by that approval. The vulnerability is possible because the REST API for approvals exposes the live external prompt link without verifying that the requester owns the approval.

Who should check

Teams running Splunk SOAR versions below 8.8.0 with approval workflows and users who can view affected containers

“In Splunk SOAR versions below 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 Attacker holds permission to view an affected container
  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-131243 (Sensitive 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-131243 (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)
- Attacker holds permission to view an affected container (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-131243 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131243 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-131243
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-131243
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-131243"}.

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.6/10CVSS 7.6
  • 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-131243
RecordNVD · CVE-2026-131243

Questions about CVE-2026-131243

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

An attacker can obtain another user's live external prompt link through the approvals REST API. The attacker can read the approval prompt without authentication and submit a response that may disrupt or alter the automated workflow.

Source: advisory.splunk.com, cve.org

Which versions are affected by CVE-2026-131243?

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, and the attacker needs permission to view an affected container. Check the installed Splunk SOAR version to see which side of 8.8.0 a deployment is on.

Source: advisory.splunk.com, cve.org

How do I fix CVE-2026-131243?

Upgrade Splunk SOAR to version 8.8.0 or higher. No patch ids or workaround are named in the checked facts.

Source: advisory.splunk.com, cve.org

Why do the sources disagree?

The description says the approval prompt can be read without authentication, which points to an unauthenticated vector. The CVSS vector lists privileges required as low (PR:L), which means some privilege is needed. The sources do not reconcile these two points.

Source: advisory.splunk.com, cve.org

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