{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-76372 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-76372 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76372 is a medium-severity missing authorization vulnerability in Splunk Nmap Scanner, published on 19 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-76372 and fix it if it is affected.\n\nWhat it is: CVE-2026-76372 is a medium-severity missing authorization vulnerability in Splunk Nmap Scanner, published on 19 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-76372 in the wild and no public exploit code.\n\nAffected product: Splunk Nmap Scanner. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-76372/ (Markdown: https://insights.sbomify.com/CVE-2026-76372/index.md)","id":"CVE-2026-76372","markdown":"https://insights.sbomify.com/CVE-2026-76372/index.md","name":"CVE-2026-76372","record":{"aliases":["GHSA-5x32-67q6-rxx3"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk SOAR plugin","requires_auth":"high_privilege","summary":"Users with playbook editing rights can execute arbitrary commands on target systems via Nmap scripts in Safe Mode due to incorrect permission checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[],"cvss":{"score":6.6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Incorrect Permission Assignment through Safe Mode in Nmap Scanner for Splunk SOAR","id":"CVE-2026-76372","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Filter Injection through Action Parameters in AD LDAP app for Splunk SOAR","id":"CVE-2026-76373"},"packages":[],"prev":{"headline":"Incorrect Permission Assignment through Safe Mode in FireAMP for Splunk SOAR","id":"CVE-2026-76371"},"products":["Nmap Scanner"],"published":"2026-08-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-20","vendors":["Splunk"]},"summary":"Users with playbook editing rights can execute arbitrary commands on target systems via Nmap scripts in Safe Mode due to incorrect permission checks.","url":"https://insights.sbomify.com/CVE-2026-76372/"}