CVE-2026-76380: CrowdStrike OAuth API app for Splunk SOAR · The application stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Affects CrowdStrike OAuth API app for Splunk SOARSource CVE Database V5
Not known to be exploited · CVSS 4.3 Medium : upgrade to 5.1.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 5.1.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 CrowdStrike OAuth API app for Splunk SOAR to 5.1.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| SplunkCrowdStrike OAuth API app for Splunk SOAR | Affected
| Fixed in
|
AI-suggested
Upgrade to version 5.1.3 or later of the CrowdStrike OAuth API app for Splunk SOAR, where this issue is fixed by masking the document_password parameter. Until upgrading, restrict permissions to run actions only to trusted users to minimize exposure risk.
Description
CVE-2026-76380 affects the CrowdStrike OAuth API app for Splunk SOAR versions 5.1 and 5.1.x prior to 5.1.3. The vulnerability involves the exposure of a sensitive document password in cleartext within the user interface when running specific actions (detonate file or detonate url). This occurs because the document_password parameter is not masked, allowing users with permission to run actions to see the password. The issue is due to the app not marking this parameter as a password type.