CVE-2026-76381: MS Graph for Active Directory app for Splunk SOAR · The application stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Affects MS Graph for Active Directory app for Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.5.2 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.5.2
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 MS Graph for Active Directory app for Splunk SOAR to 1.5.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkMS Graph for Active Directory app for Splunk SOAR | Affected
| Fixed in
|
AI-suggested
Upgrade the MS Graph for Active Directory app for Splunk SOAR to version 1.5.2 or later, where this issue is fixed by properly masking the temp_password parameter. If you cannot patch yet, restrict permissions to run actions to trusted users only.
Description
CVE-2026-76381 affects the MS Graph for Active Directory app for Splunk SOAR versions 1.5 and 1.5.x prior to 1.5.2. The vulnerability allows users with permission to run actions to see a sensitive password in cleartext within the user interface when invoking the reset password action. This occurs because the app does not mask the temp_password parameter, which is not marked as a password field. The issue leads to information disclosure but does not affect integrity or availability.