Skip to main content
VulnerabilityPublished

CVE-2026-131280: Splunk SOAR · The software does not perform an authorization check when an actor attempts to access a resource or

Affects Splunk SOARSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 8.8.0 when convenient.

Data as of 19 Nov 2026, 20:22 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (cisco)CVSS 3.16.5
Patch
Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Splunk SOAR to 8.8.0.

Affected software

ProductAffectedFixed in
SplunkSplunk SOARAffected
  • <8.8.0
Fixed in
  • 8.8.0

AI-suggested

Upgrade Splunk SOAR to version 8.8.0 or later, where this authorization flaw is fixed. No other mitigations are indicated by the vendor advisory.

Description

CVE-2026-131280 affects Splunk SOAR versions prior to 8.8.0. It allows an authenticated user with the system_settings:view permission but without assets:view permission to access sensitive asset and application inventory data, tenant identifiers, connector run messages, and stored configuration snapshots via the ingestion status REST API. This occurs because the API enforces system_settings:view but does not check assets:view or tenant restrictions before returning asset-derived ingestion records. The vulnerability is fixed in version 8.8.0.

References

Community reviews

Loading reviews…