In versions below 2.3.8 of the AD LDAP 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.3.8 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.3.8
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 AD LDAP app for Splunk SOAR to 2.3.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkAD LDAP app for Splunk SOAR | Affected
| Fixed in
|
AI-suggested
A fix is available in version 2.3.8 of the AD LDAP app for Splunk SOAR. Users should upgrade to version 2.3.8 or later to remediate this issue. No cloud service remediation applies as this is not a cloud service. Patch status is not explicitly confirmed by a vendor advisory in the provided data, so verify with the vendor for official patch details.
Description
In versions below 2.3.8 of the AD LDAP app for Splunk SOAR, users with roles permitting action execution could cause sensitive Active Directory response data to be written to a persistent debug log file. This vulnerability involves unintended logging of sensitive information during write operations triggered through the app.