MCP NMAP Server has an Injection vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-3484: 3.30% estimated exploitation activity in the next 30 days; percentile 88.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A vulnerability was detected in PhialsBasement nmap-mcp-server up to bee6d23547d57ae02460022f7c78ac0893092e38. Affected by this issue is the function childprocess.exec of the file src/index.ts of the component Nmap CLI Command Handler. The manipulation results in command injection. The attack may be performed from remote. This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed. The patch is identified as 30a6b9e1c7fa6146f51e28d6ab83a2568d9a3488. It is best practice to apply a patch to resolve this issue.

Published by the source

3 Mar 2026, 21:31 UTC

Last modified by the source

6 Mar 2026, 01:01 UTC

Source last checked

26 Oct 2026, 12:43 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xc68-rrqc-qgq3

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xc68-rrqc-qgq3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-3484

Advisory: MCP NMAP Server has an Injection vulnerability
IDs: CVE-2026-3484, GHSA-xc68-rrqc-qgq3
Record: https://patchnext.com/advisories/cve-2026-3484 (revision 3, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm mcp-nmap-server: affected <= 1.0.1

## Suggested inspection (read-only)
- `npm ls mcp-nmap-server --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mcp-nmap-server.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xc68-rrqc-qgq3 (OSV record GHSA-xc68-rrqc-qgq3 lists affected ranges: npm mcp-nmap-server >=0 <=1.0.1)
- Verified: https://github.com/advisories/GHSA-xc68-rrqc-qgq3 (GitHub-reviewed advisory GHSA-xc68-rrqc-qgq3 lists affected ranges: npm mcp-nmap-server >=0 <=1.0.1)

Commands are suggestions: review each one before running it.