CVE-2026-76380: Information Disclosure through Action Parameters in CrowdStrike OAuth API app for Splunk SOAR

Published Aug 19, 2026
·
Updated

In versions below 5.1.3 of the CrowdStrike OAuth API app for Splunk SOAR, a user who holds a role with permission to run actions could expose a sensitive document password by invoking either the detonate file or detonate url action, because the action's documentpassword parameter is not masked and is shown in cleartext in the user interface. The information disclosure is possible because the app does not mark the affected action parameter as a password. For more information see Run an action in Splunk SOAR (https://help.splunk.com/en/splunk-soar/soar-on-premises/use-splunk-soar-on-premises/8.6.0/use-the-command-line-interface-to-perform-tasks-in-splunk-soar-on-premises/run-an-action-in-splunk-soar-on-premises).

Affected Software

1 affected component
CrowdStrike CrowdStrike OAuth API app for Splunk SOAR<5.1.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade CrowdStrike OAuth API app for Splunk SOAR to a version that resolves this vulnerability.

    Fixed in 5.1.3

Event History

Aug 19, 2026
CVE Published
via MITRE·09:35 PM
Data Sourced
via MITRE·09:35 PM
RemedyDescriptionSeverityWeakness

Frequently Asked Questions

1

Who can expose the sensitive document password?

A user with a Splunk SOAR role that has permission to run actions can expose it by invoking the affected detonate file or detonate url action.

2

Which deployments are affected?

Versions of the CrowdStrike OAuth API app for Splunk SOAR below 5.1.3 are affected. The issue applies when the affected actions are used with the document_password parameter.

3

What should be done if the app cannot be updated immediately?

Restrict permission to run actions for users who do not need to invoke the detonate file or detonate url actions, and avoid supplying sensitive document passwords through the affected parameter where possible.

4

How can an organization determine whether a password may have been exposed?

Review use of the detonate file and detonate url actions in affected app versions, especially executions that supplied document_password. In vulnerable versions, that parameter is displayed in cleartext in the user interface.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203