Splunk SOAR account takeover via leaked reset credential in REST API
Splunk SOAR versions below 8.8.0 log password-reset email bodies without redacting them, which lets an Observer-role user reach reset credentials. Fixed in 8.8.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.8.0
- Who is exposed
- Specific setups only
Summary
Splunk SOAR has an information exposure flaw in its REST API that lets a remote attacker who logs in with a low-privilege Observer account read a password-reset credential from a diagnostic log bundle and use it to reset the password of an active local account. The flaw exists because the product does not redact password-reset email bodies before logging communications between its processes.
Written by a model
Original description
In Splunk SOAR versions below 8.8.0, a user who holds the "Observer" Splunk SOAR role could access a password-reset credential in a diagnostic log bundle and reset the password for an active local account. The vulnerability is possible because Splunk SOAR does not redact password-reset email bodies before it logs communications between product processes.
Who should check
Teams running Splunk SOAR below 8.8.0, especially any instance with users holding the Observer role.
“In Splunk SOAR versions below 8.8.0”
What to do
Check whether your setup matches what the bug needs.
Splunk SOAR versions below 8.8.0 Splunk SOAR logs password-reset email bodies without redacting themUpgrade 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-131282 (Information Exposure 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-131282 (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)
- Splunk SOAR logs password-reset email bodies without redacting them (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-131282 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131282 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-131282
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-131282
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-131282"}.Affected versions
- Splunk Splunk SOARfixed in 8.8.0
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | advisory.splunk.com · advisories/SVD-2026-1108 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-131282 |
| Record | NVD · CVE-2026-131282 |
Questions about CVE-2026-131282
Is CVE-2026-131282 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?
Splunk SOAR does not redact password-reset email bodies before it logs communications between product processes. A user with the Observer role can get a password-reset credential from a diagnostic log bundle and use it to reset the password for an active local account.
Source: advisory.splunk.com, cve.org
Which versions are affected by CVE-2026-131282?
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 in scope. To check the version, look at the installed Splunk SOAR release in the product.
Source: advisory.splunk.com, cve.org
How do I fix CVE-2026-131282?
Upgrade Splunk SOAR to version 8.8.0 or higher.
Source: advisory.splunk.com, cve.org
Related
- 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
- CVE-2026-131297Single Sign-On Authentication Bypass in Splunk SOAR
- CVE-2026-131288[Flashpoint] Privilege Escalation through HAProxy Cluster Operations in Splunk SOAR
- CVE-2026-131278Sensitive Information Disclosure through App Editor Debug Actions in Splunk SOAR
No corrections so far. Something wrong on this page? Report an error.