CVE-2026-72712 Nmap Project CVE debrief

Who should care

Defenders responsible for maintaining Nmap installations should assess exposure and prioritize patching to prevent potential crashes. This includes verifying Nmap versions, implementing compensating controls, and monitoring for potential crashes. Security teams and vulnerability management teams should also review the CVE record and NVD vulnerability detail page for additional information on the vulnerability and potential fixes.

Why it matters

A denial of service vulnerability exists in Nmap versions up to and including 7.99. Defenders should prioritize verifying Nmap versions and applying patches to prevent potential crashes.

• Potential application crashes require verification and patching to prevent denial of service
• Defenders must verify Nmap versions and implement compensating controls to prevent exploitation

Technical summary

The vulnerability exists in Nmap versions up to and including 7.99. A remote attacker can crash the application by sending a crafted packet with a zero-length TCP option, causing an out-of-memory condition. The vulnerability is triggered by a malformed packet that forces the Packet:parse_options() function in nselib/packet.lua to allocate objects in an infinite loop. This results in an out-of-memory condition that leads to application crash. Defenders should prioritize verifying Nmap versions and applying patches to prevent potential crashes.

Defensive priority

Defenders should prioritize verifying Nmap versions and applying patches to prevent potential crashes.

Recommended defensive actions

• Verify Nmap versions and apply patches
• Monitor for potential crashes
• Implement compensating controls to prevent exploitation
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The vulnerability is described in the CVE record and NVD vulnerability detail page. The source references provide additional information on the vulnerability and potential fixes. Defenders should verify Nmap versions and apply patches to prevent potential crashes. The CVE record was published on 2026-08-11T18:18:23.550Z and has not been modified since then. The source references provide additional context on the vulnerability, but the information is limited, and defenders should exercise caution when assessing exposure.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.