CVE-2026-76372: Incorrect Permission Assignment through Safe Mode in Nmap Scanner for Splunk SOAR

Published Aug 19, 2026
·
Updated

In Nmap Scanner versions below 3.0.15, a user who holds a role that can edit, create, or run playbooks in Splunk SOAR could run the scan network action in a Safe Mode playbook while that action is listed as read-only, which could allow for command execution or other changes on a target system through Nmap Scripting Engine scripts. The vulnerability is possible because the Nmap Scanner connector action manifest classifies the scan network action as read-only even though the action accepts script parameters that can perform write operations. For more information see Manage settings for a playbook in Splunk SOAR (https://help.splunk.com/en/splunk-soar/soar-cloud/build-playbooks/manage-playbooks-and-playbook-settings/manage-settings-for-a-playbook-in-splunk-soar-cloud) in the Splunk documentation.

Affected Software

1 affected component
Splunk Nmap Scanner<3.0.15

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Splunk SOAR Nmap Scanner connector to a version that resolves this vulnerability.

    Fixed in 3.0.15

Event History

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

Frequently Asked Questions

1

Who can exploit this issue?

A Splunk SOAR user with a role that can edit, create, or run playbooks can exploit it by running the scan network action from a Safe Mode playbook.

2

What conditions are required for exploitation?

The affected Nmap Scanner version must be below 3.0.15, and the user must be able to supply Nmap Scripting Engine script parameters to the scan network action. No user interaction is described.

3

Why does Safe Mode not prevent the risky behavior?

The connector action manifest marks scan network as read-only, allowing it in a Safe Mode playbook. However, its script parameters can invoke Nmap Scripting Engine scripts capable of write operations, including command execution or other changes on the target system.

4

Which systems may be affected by the resulting actions?

The potential command execution or changes occur on the target system scanned through the Nmap action. The issue can affect confidentiality, integrity, and availability of that target.

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