Skip to main content
CVE-2026-131276VulnerabilityPublished

In Splunk SOAR versions below 8.8.0, an authenticated user that holds a role with the System Settings view permission

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131276· Medium 4.3

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

Data as of 19 Nov 2026, 22:34 UTC

CVSS 3.1 base score
4.3Medium
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.14.3
Patch
Available – fixed in 8.8.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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 19 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

Since this affects versions below 8.8.0, upgrading to version 8.8.0 or later is recommended if such a version includes a fix. Until an official fix is confirmed, restrict roles to prevent users from having the System Settings view permission without the Assets view permission, or limit access to the ingestion history view to trusted users only. Monitor vendor advisories for official remediation guidance.

Description

Splunk SOAR versions below 8.8.0 contain an authorization vulnerability where authenticated users with the System Settings view permission but without the Assets view permission can access asset and tenant metadata via the ingestion history view. This occurs because the ingestion history view does not properly restrict summary results to only those assets and tenants the user is authorized to view.

References

Community reviews

Loading reviews…