Skip to main content
Mallory
CriticalVulnerability

CVE-2009-2532: SMBv2 Command Value Vulnerability (CVE-2009-2532)

Published Oct 14, 2009 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS10.0Critical · v2
EPSS62.2%99th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2009-2532CWE-20

CVE-2009-2532 is a remote code execution vulnerability in the Microsoft Windows implementation of SMBv2. Specifically, Windows Vista (Gold, SP1, SP2), Windows Server 2008 (Gold, SP2), and Windows 7 RC do not properly process the command value in an SMB Multi-Protocol Negotiate Request packet. An attacker can exploit this flaw by sending a specially crafted SMBv2 packet to the Server service, resulting in arbitrary code execution with SYSTEM privileges. The vulnerability is due to improper validation of the command field in SMBv2 requests, leading to memory corruption.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote, unauthenticated attackers to execute arbitrary code in the context of the Server service, typically with SYSTEM-level privileges. This can result in full system compromise, including installation of malware, data theft, privilege escalation, and lateral movement within a network. The vulnerability is wormable and can be exploited without user interaction, making it highly critical for enterprise environments.

Mitigation

If you can’t patch tonight, do this now.

Until patches can be applied, disable SMBv2 on affected systems to prevent exploitation. Additionally, restrict inbound SMB traffic at network boundaries using firewalls or access control lists. Monitor for suspicious SMB traffic and review logs for signs of exploitation attempts. Ensure that only trusted hosts can communicate with SMB services.

Remediation

Patch, then assume compromise.

Apply the security updates provided by Microsoft as detailed in the relevant security bulletin for CVE-2009-2532. Ensure all affected systems (Windows Vista, Windows Server 2008, Windows 7 RC) are patched. If patching is not immediately possible, consider disabling SMBv2 as a temporary workaround, though this may impact network functionality. Restrict access to SMB services from untrusted networks using firewalls or network segmentation.

Public exploits

Exploits

No validated public exploits yet. Hidden: 2 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Vistaoperating_system
FAQ

Frequently asked questions

Is CVE-2009-2532 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-2532 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-2532?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2009-2532. 2 candidate exploit records are not yet analyzed.
Is there a patch for CVE-2009-2532?
Apply the security updates provided by Microsoft as detailed in the relevant security bulletin for CVE-2009-2532. Ensure all affected systems (Windows Vista, Windows Server 2008, Windows 7 RC) are patched.
What products are affected by CVE-2009-2532?
Microsoft Corporation Windows Server 2008 and Microsoft Corporation Windows Vista.
How severe is CVE-2009-2532?
CVE-2009-2532 has a CVSS v2 score of 10.0 (Critical) and an EPSS score of 62.2% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.