Microsoft XML Core Services (aka MSXML) 3.0 does not properly handle HTTP responses, which allows remote attackers to execute arbitrary cod…

published 2010-08-11 16y ago modified 2026-06-16 4mo ago also EUVD-2010-2565

cvss: 9.3; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 24.9%; EPSS 24.9% chance of exploitation in 30 days, percentile 97%
public exploits: 1; Exploit-DB

Microsoft XML Core Services (aka MSXML) 3.0 does not properly handle HTTP responses, which allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted response, aka "Msxml2.XMLHTTP.3.0 Response Handling Memory Corruption Vulnerability."

Is CVE-2010-2561 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

2010-08-10 First public exploit (EDB-14609)
2010-08-11 Published

Exploit prediction

24.87% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

EDB-14609 Microsoft Msxml2.XMLHTTP.3.0 - Response Handling Memory Corruption (MS10-051) dos, 2010-08-10

CVSS scores

assigned by	version	score	vector
NVD	2.0	9.3	AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-94 Improper Control of Generation of Code

References

docs.microsoft.com /en-us/security-updates/securitybulletins/2010/ms10-051
vendor-advisory
us-cert.gov /cas/techalerts/TA10-222A.html
third-party-advisory, us-government-resource
oval.cisecurity.org /repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11730
vdb-entry, signature

Sources

CVE List CVE-2010-2561
NVD CVE-2010-2561

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.