In versions below 2.5.3 of the Azure AD Graph app for Splunk SOAR, a user who holds a role with permission to run
Source GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 2.5.3 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 2.5.3
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 Azure AD Graph app for Splunk SOAR to 2.5.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkAzure AD Graph app for Splunk SOAR | Affected
| Fixed in
|
AI-suggested
A fix is available in version 2.5.3 of the Azure AD Graph app for Splunk SOAR. Users should upgrade to version 2.5.3 or later to ensure the temp_password parameter is properly masked. No other mitigation steps are indicated.
Description
In versions below 2.5.3 of the Azure AD Graph app for Splunk SOAR, a vulnerability exists where a user with permission to run actions can see a sensitive password in cleartext. This occurs because the reset password action's temp_password parameter is not masked in the user interface, leading to information disclosure. The app fails to mark this parameter as a password, exposing the temporary password to authorized users who run the action.