Incorrect Permission Assignment through Safe Mode in Nmap Scanner for Splunk SOAR (CVE-2026-76372) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-76372

Incorrect Permission Assignment through Safe Mode in Nmap Scanner for Splunk SOAR

Answer in brief

CVE-2026-76372 records a Unknown severity vulnerability in Incorrect Permission Assignment through Safe Mode in Nmap Scanner for Splunk SOAR. The current sources do not mark it as known exploited. The current feed maps Splunk/Nmap Scanner (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 19, 2026Updated Aug 19, 2026Source checked Aug 19, 2026First seen by HOL Aug 19, 2026Material review Aug 19, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Splunk/Nmap Scanner (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Splunk/Nmap Scannergeneric	>=3.0 <3.0.15	3.0.15

Recommended response

Check inventory. Check lockfiles and deployed manifests for Splunk/Nmap Scanner.
Review the reported fix. Update Splunk/Nmap Scanner to 3.0.15 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 19, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 19, 2026

Sources and claim methodology

Source referenceadvisory.splunk.com

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.