In versions below 2.2.1 of the Splunk Attack Analyzer Connector for Splunk SOAR, a user who holds a role with
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.2.1 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- 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:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 Attack Analyzer Connector for Splunk SOAR to 2.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkSplunk Attack Analyzer Connector for Splunk SOAR | Affected
| Fixed in
|
AI-suggested
A fix is available in version 2.2.1 of the Splunk Attack Analyzer Connector for Splunk SOAR, which addresses the issue by properly masking the archive_password parameter. Users should upgrade to version 2.2.1 or later to remediate this vulnerability. Until then, restrict roles with permission to run actions to trusted users only. Patch status is not explicitly confirmed in the input data, so verify the vendor advisory for the latest remediation guidance.
Description
A vulnerability in versions below 2.2.1 of the Splunk Attack Analyzer Connector for Splunk SOAR allows users with permission to run actions to see a sensitive archive password in cleartext. This occurs because the archive_password parameter in the detonate file and detonate url actions is not masked in the user interface. The issue arises from the app not marking this parameter as a password, leading to information disclosure.