In versions below 2.2.1 of the Splunk Attack Analyzer Connector for Splunk SOAR, a user who holds a role with permission to run actions could expose… (CVE-2026-76384)
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.
AI Analysis
Technical Summary
In Splunk Attack Analyzer Connector for Splunk SOAR versions prior to 2.2.1, the archive_password parameter used in the detonate file and detonate url actions is exposed in cleartext to users who have roles permitting them to run these actions. This is due to the parameter not being designated as a password field, resulting in sensitive information being displayed unmasked in the user interface. The vulnerability is identified as CWE-312 (Cleartext Storage of Sensitive Information).
Potential Impact
The vulnerability allows users with action execution permissions to view sensitive archive passwords in cleartext within the user interface. This information disclosure could lead to unauthorized access if the exposed password is reused or leveraged in other contexts. There is no indication of impact on integrity or availability. The CVSS score is 4.3 (medium severity), reflecting a network attack vector with low complexity and requiring privileges to run actions.
Mitigation Recommendations
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.
In versions below 2.2.1 of the Splunk Attack Analyzer Connector for Splunk SOAR, a user who holds a role with permission to run actions could expose… (CVE-2026-76384)
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.
CVSS v3.1
Score 4.3medium
Affected software
pkg:github/splunk/attack-analyzer-connectorRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In Splunk Attack Analyzer Connector for Splunk SOAR versions prior to 2.2.1, the archive_password parameter used in the detonate file and detonate url actions is exposed in cleartext to users who have roles permitting them to run these actions. This is due to the parameter not being designated as a password field, resulting in sensitive information being displayed unmasked in the user interface. The vulnerability is identified as CWE-312 (Cleartext Storage of Sensitive Information).
Potential Impact
The vulnerability allows users with action execution permissions to view sensitive archive passwords in cleartext within the user interface. This information disclosure could lead to unauthorized access if the exposed password is reused or leveraged in other contexts. There is no indication of impact on integrity or availability. The CVSS score is 4.3 (medium severity), reflecting a network attack vector with low complexity and requiring privileges to run actions.
Mitigation Recommendations
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.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-6cqf-6324-39pj
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-76384"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a870a86acd9273b49b5a0f8
Added to database: 08/20/2026, 14:09:10 UTC
Last enriched: 08/20/2026, 14:43:51 UTC
Last updated: 08/20/2026, 21:51:58 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.