In versions below 2.1.4 of the Venafi app for Splunk SOAR, a user who holds a role with permission to run actions
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.1.4 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.1.4
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 Venafi app for Splunk SOAR to 2.1.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkVenafi app for Splunk SOAR | Affected
| Fixed in
|
AI-suggested
Upgrade to version 2.1.4 or later of the Venafi app for Splunk SOAR where this issue is fixed. Since the vulnerability is due to unmasked parameters, applying the official fix will prevent password exposure. No other mitigations are specified.
Description
In versions below 2.1.4 of the Venafi app for Splunk SOAR, a user with permission to run actions can see keystore and private-key passwords in cleartext when invoking the get certificate action. This occurs because the app does not mask the keystore_password and password parameters in the user interface, leading to information disclosure.