CVE-2026-76375: AD LDAP app for Splunk SOAR · Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
Affects AD LDAP app for Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 5.0 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:C/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
Upgrade the AD LDAP app for Splunk SOAR to version 2.3.8 or later, where this issue is resolved. Users should avoid running actions that trigger logging of the full connector process environment in affected versions. Since this is an on-premises app, remediation requires applying the official update from Splunk.
Description
CVE-2026-76375 affects the AD LDAP app for Splunk SOAR versions 2.3 and from 2.3 up to but not including 2.3.8. In these versions, a user with permission to run actions can cause sensitive credentials to be written in plaintext to a persistent debug log file by invoking a specific action. This exposure arises because the full connector process environment is logged, potentially revealing sensitive information. The vulnerability has a medium severity with a CVSS score of 5. No known exploits are reported in the wild. The issue is fixed in version 2.3.8 or later.