Skip to main content
Menu
CVEs

Splunk SOAR root privilege escalation via HAProxy cluster operations

Splunk SOAR versions below 8.8.0 with a configured load balancer are affected. Fixed in Splunk SOAR 8.8.0.

CVE-2026-131288EUVD-2026-130553Published November 19, 2026, updated

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

Summary

Splunk SOAR is affected. A user with low-level access to the configured load balancer account can replace a helper file that Splunk SOAR later runs with root privileges during cluster lifecycle operations, so when a Splunk SOAR administrator performs such an operation, the attacker can run arbitrary code as root on the load balancer. The attack requires local access, and it also depends on an administrator taking that action.

Written by a model

Original description

In Splunk SOAR versions below 8.8.0, a user with access to the configured load balancer account could replace a load balancer helper that Splunk SOAR later runs with root privileges during cluster lifecycle operations. If a Splunk SOAR administrator performs a cluster lifecycle operation, Splunk SOAR could execute arbitrary code with root privileges on the load balancer. The vulnerability is possible because Splunk SOAR does not verify the integrity or ownership of the load balancer helper before running it with root privileges.

Who should check

Teams running Splunk SOAR below 8.8.0 that manage a load balancer cluster through Splunk SOAR cluster lifecycle operations

“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 A Splunk SOAR administrator performs a cluster lifecycle operation with a configured load balancer
  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-131288 ([Flashpoint] Privilege Escalation through HAProxy Cluster Operations 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-131288 (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 Splunk SOAR administrator performs a cluster lifecycle operation with a configured load balancer (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: local access, low-privilege login, a user action.
CISA KEV: CVE-2026-131288 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131288 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-131288
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-131288
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-131288"}.

Affected versions

cve.now Index

13Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.3/10CVSS 7.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 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
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

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-131288
RecordNVD · CVE-2026-131288

Questions about CVE-2026-131288

Is CVE-2026-131288 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 access to the configured load balancer account can replace a load balancer helper that Splunk SOAR runs as root. When a SOAR administrator performs a cluster lifecycle operation, SOAR can then run arbitrary code with root privileges on the load balancer.

Source: advisory.splunk.com, cve.org

Which versions are affected by CVE-2026-131288?

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 that have a load balancer configured. To check, look at the installed Splunk SOAR version and whether a load balancer is configured for the cluster.

Source: advisory.splunk.com, cve.org

How do I fix CVE-2026-131288?

Upgrade Splunk SOAR to version 8.8.0 or higher.

Source: advisory.splunk.com, cve.org

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