CVE-2010-2552

CVE-2010-2552 is a high-severity vulnerability in Microsoft Windows 7 with a CVSS 2.0 base score of 7.8. Its EPSS exploit-prediction score of 33% places it in the 98th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-399.

Key facts

Description

Stack consumption vulnerability in the SMB Server in Microsoft Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 allows remote attackers to cause a denial of service (system hang) via a malformed SMBv2 compounded request, aka "SMB Stack Exhaustion Vulnerability."

Frequently asked questions

What is CVE-2010-2552?
Stack consumption vulnerability in the SMB Server in Microsoft Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, and R2, and Windows 7 allows remote attackers to cause a denial of service (system hang) via a malformed SMBv2 compounded request, aka "SMB Stack Exhaustion Vulnerability."
How severe is CVE-2010-2552?
CVE-2010-2552 has a CVSS 2.0 base score of 7.8, rated high severity.
Is CVE-2010-2552 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 33% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-2552?
CVE-2010-2552 primarily affects Microsoft Windows 7. In total, 13 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2010-2552?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2010-2552 published?
CVE-2010-2552 was published on 2010-08-11 and last updated on 2026-06-16.

References

Affected products (13)

More vulnerabilities in Microsoft Windows 7

All CVEs affecting Microsoft Windows 7 →

Other CWE-399 (Resource Management Errors) vulnerabilities

Browse all CWE-399 (Resource Management Errors) vulnerabilities →