CVE-2026-76373: AD LDAP app for Splunk SOAR · The software constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.
Affects AD LDAP app for Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 5.4 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 16% 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:L/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 fixed version is available starting from version 2.3.8. Users should upgrade the AD LDAP app for Splunk SOAR to version 2.3.8 or later to remediate this vulnerability. No additional mitigation steps are indicated in the provided data.
Description
CVE-2026-76373 affects the AD LDAP app for Splunk SOAR versions 2.3 and from 2.3 up to but not including 2.3.8. It allows a user with permission to run actions to inject crafted input into LDAP queries, potentially enumerating Active Directory objects, reading sensitive attributes, and redirecting account modification actions to unintended objects. The vulnerability arises from improper neutralization of special elements in LDAP queries constructed from externally influenced input.