Skip to main content
VulnerabilityPublished

CVE-2026-131305: Splunk AI Assistant · One or more system settings or configuration elements can be externally controlled by a user

Affects Splunk AI AssistantSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 2.0.0 soon.

Data as of 19 Nov 2026, 20:20 UTC

CVSS 3.1 base score
8.1High
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.18.1
Patch
Available – fixed in 2.0.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 AI Assistant to 2.0.0.

Affected software

ProductAffectedFixed in
SplunkSplunk AI AssistantAffected
  • <2.0.0
Fixed in
  • 2.0.0

AI-suggested

Upgrade Splunk AI Assistant to version 2.0.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated.

Description

CVE-2026-131305 affects Splunk AI Assistant versions prior to 2.0.0. It allows users without admin or power roles to modify certain system settings via the REST API by submitting client-controlled feature settings. This occurs because the API does not enforce server-side configuration boundaries properly. The vulnerability can lead to unauthorized modification of response metadata. A fix is available in version 2.0.0.

References

Community reviews

Loading reviews…