Skip to main content
VulnerabilityPublished

CVE-2026-76384: Splunk Attack Analyzer Connector for Splunk SOAR · The application stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

Affects Splunk Attack Analyzer Connector for Splunk SOARSource CVE Database V5

0
Compare

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

Data as of 16 Nov 2026, 20:25 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.1
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 Aug 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 16 Nov 2026.

What to do

Upgrade Splunk Attack Analyzer Connector for Splunk SOAR to 2.2.1.

Affected software

ProductAffectedFixed in
SplunkSplunk Attack Analyzer Connector for Splunk SOARAffected
  • >=2.2 <2.2.1
Fixed in
  • 2.2.1

AI-suggested

Upgrade to version 2.2.1 or later of the Splunk Attack Analyzer Connector for Splunk SOAR, where this issue is fixed by properly masking the archive_password parameter. Until then, restrict permissions to run the affected actions to trusted users only. Patch status is confirmed fixed in 2.2.1.

Description

CVE-2026-76384 affects the Splunk Attack Analyzer Connector for Splunk SOAR versions prior to 2.2.1. The vulnerability involves the exposure of a sensitive archive password in cleartext within the user interface when invoking certain actions. This occurs because the archive_password parameter is not masked or treated as a password field, allowing users with permission to run actions to see the password in cleartext. The issue is limited to versions below 2.2.1.

References

Community reviews

Loading reviews…