Skip to main content
CVE-2026-76381VulnerabilityPublished

In versions below 1.5.2 of the MS Graph for Active Directory app for Splunk SOAR, a user who holds a role with

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-76381· Medium 4.3

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

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
SplunkMS Graph for Active Directory app for Splunk SOARAffected
  • >=1.5 <1.5.2
Fixed in
  • 1.5.2

AI-suggested

A fix is available in version 1.5.2 of the MS Graph for Active Directory app for Splunk SOAR, which addresses this issue by properly masking the temp_password parameter. Users should upgrade to version 1.5.2 or later to remediate this vulnerability. No other mitigation guidance is provided or necessary.

Description

In versions below 1.5.2 of the MS Graph for Active Directory app for Splunk SOAR, a sensitive password may be exposed in cleartext in the user interface. This occurs because the reset password action's temp_password parameter is not masked, allowing users with permission to run actions to see the password. The vulnerability is due to the app not marking this parameter as a password field.

References

Community reviews

Loading reviews…