Skip to main content
Mallory
CriticalVulnerability

CVE-2010-0028: MS Paint Integer Overflow Vulnerability

Published Feb 10, 2010 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v2
EPSS48.3%99th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2010-0028CWE-190

An integer overflow vulnerability exists in Microsoft Paint on Windows 2000 SP4, XP SP2 and SP3, and Server 2003 SP2. The flaw is triggered when Paint processes a specially crafted JPEG (.JPG) file, leading to an integer overflow condition. This can result in memory corruption and potentially allow an attacker to execute arbitrary code in the context of the user running Paint.

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 attackers to execute arbitrary code with the privileges of the user who opens a malicious JPEG file in Microsoft Paint. This could lead to full compromise of the affected system if the user has administrative privileges.

Mitigation

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

As a temporary mitigation, users should avoid opening JPEG files from untrusted sources in Microsoft Paint. Employing least privilege principles and using non-administrative accounts for daily activities can reduce the impact of exploitation.

Remediation

Patch, then assume compromise.

Apply the security updates provided by Microsoft for the affected Windows versions. Users should ensure their systems are fully patched and avoid opening untrusted JPEG files in Paint until the patch is applied.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 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 2000operating_system
Microsoft CorporationWindows Server 2003operating_system
Microsoft CorporationWindows Xpoperating_system
FAQ

Frequently asked questions

Is CVE-2010-0028 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2010-0028 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2010-0028?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2010-0028. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2010-0028?
Apply the security updates provided by Microsoft for the affected Windows versions. Users should ensure their systems are fully patched and avoid opening untrusted JPEG files in Paint until the patch is applied.
What products are affected by CVE-2010-0028?
Microsoft Corporation Windows 2000, Microsoft Corporation Windows Server 2003, and Microsoft Corporation Windows Xp.
How severe is CVE-2010-0028?
CVE-2010-0028 has a CVSS v2 score of 9.3 (Critical) and an EPSS score of 48.3% (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.