Skip to main content
CVE-2026-76380VulnerabilityPublished

In versions below 5.1.3 of the CrowdStrike OAuth API app for Splunk SOAR, a user who holds a role with permission to

Source GCVE Database

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

Not known to be exploited · CVSS 4.3 Medium : upgrade to 5.1.3 when convenient.

Data as of 16 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 5.1.3
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 16 Nov 2026.

What to do

Upgrade CrowdStrike OAuth API app for Splunk SOAR to 5.1.3.

Affected software

ProductAffectedFixed in
SplunkCrowdStrike OAuth API app for Splunk SOARAffected
  • >=5.1 <5.1.3
Fixed in
  • 5.1.3

AI-suggested

A fix is available in version 5.1.3 of the CrowdStrike OAuth API app for Splunk SOAR. Users should upgrade to version 5.1.3 or later to ensure the document_password parameter is properly masked. Until then, restrict roles with permission to run actions to trusted users only. Patch status is not explicitly confirmed in vendor advisories here; verify with the vendor for official remediation guidance.

Description

In versions below 5.1.3 of the CrowdStrike OAuth API app for Splunk SOAR, a vulnerability exists where the document_password parameter in the detonate file and detonate url actions is not masked. This causes the sensitive password to be displayed in cleartext in the user interface to users with permission to run actions. The issue arises because the app does not designate the parameter as a password type, leading to information disclosure.

References

Community reviews

Loading reviews…