Description
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.
Published: 2026-08-19
Score: 6.6 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in the Nmap Scanner connector for Splunk SOAR allows a user who can edit, create, or run playbooks to execute network scans in Safe Mode playbooks that are incorrectly marked as read‑only. Because the scan network action accepts script parameters that can perform write operations, the attacker can run arbitrary commands on the target system. This results in unauthorized command execution, a violation of confidentiality, integrity, and availability. The weakness is classified as CWE‑732, Incorrect Permission Assignment.

Affected Systems

Splunk SOAR users with the Connector: Nmap Scanner installed in versions earlier than 3.0.15 are affected. Any playbook that includes the scan network action as read‑only in this version can be abused.

Risk and Exploitability

The CVSS score of 6.6 indicates a moderate severity. EPSS is not available and the vulnerability is not listed in CISA KEV. The likely attack vector requires an authenticated Splunk SOAR user with playbook creation or editing permissions, so the risk is confined to environments where such roles are assigned. The exploit would involve adding or modifying a Safe Mode playbook to invoke the scan network action with parameters that trigger executable scripts on the target. The impacts are limited to systems reachable by the Nmap scan and do not require external network access to the Splunk platform itself.

Generated by OpenCVE AI on August 20, 2026 at 10:43 UTC.

Remediation

Vendor Solution

Upgrade each affected Splunk SOAR connector to the applicable fixed version listed in Product Status.


Vendor Workaround

Turn off or remove the Nmap Scanner app for Splunk SOAR. For more information see [Add and configure apps and assets to provide actions in Splunk SOAR](https://help.splunk.com/en/splunk-soar/soar-cloud/administer-soar-cloud/manage-your-splunk-soar-cloud-apps-and-assets/add-and-configure-apps-and-assets-to-provide-actions-in-splunk-soar-cloud) in the Splunk documentation. Note: Turning off the app stops all actions configured through it from running.


OpenCVE Recommended Actions

  • Upgrade the Nmap Scanner connector to version 3.0.15 or later, as per Splunk’s recommendation.
  • If an upgrade cannot be performed immediately, disable or remove the Nmap Scanner app from the Splunk SOAR environment to block its use in playbooks.
  • Limit or revoke playbook edit, create, and run permissions from users who do not need them, ensuring only trusted users can manage playbooks.

Generated by OpenCVE AI on August 20, 2026 at 10:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 21 Aug 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Thu, 20 Aug 2026 09:30:00 +0000

Type Values Removed Values Added
First Time appeared Splunk
Splunk nmap Scanner
Vendors & Products Splunk
Splunk nmap Scanner

Wed, 19 Aug 2026 21:45:00 +0000

Type Values Removed Values Added
Description 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.
Title Incorrect Permission Assignment through Safe Mode in Nmap Scanner for Splunk SOAR
Weaknesses CWE-732
References
Metrics cvssV3_1

{'score': 6.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L'}


Subscriptions

Splunk Nmap Scanner
cve-icon MITRE

Status: PUBLISHED

Assigner: cisco

Published:

Updated: 2026-08-20T16:27:32.776Z

Reserved: 2026-08-19T12:02:03.630Z

Link: CVE-2026-76372

cve-icon Vulnrichment

Updated: 2026-08-20T16:22:12.400Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-08-19T22:17:23.050

Modified: 2026-08-20T17:19:46.520

Link: CVE-2026-76372

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-20T10:45:03Z

Weaknesses
  • CWE-732

    Incorrect Permission Assignment for Critical Resource