How severe is CVE-2006-4494?

CVE-2006-4494 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2006-4494 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 22% (97th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2006-4494?

CVE-2006-4494 primarily affects Microsoft Visual Studio. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2006-4494?

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-2006-4494 published?

CVE-2006-4494 was published on 2006-08-31 and last updated on 2026-06-16.

CVE-2006-4494

CVE-2006-4494 is a high-severity vulnerability in Microsoft Visual Studio with a CVSS 2.0 base score of 7.5. Its EPSS exploit-prediction score of 22% places it in the 97th percentile, indicating an elevated likelihood of exploitation.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 22% (97th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Microsoft Visual Studio
Published: 2006-08-31
Last modified: 2026-06-16

Description

Microsoft Visual Studio 6.0 allows remote attackers to cause a denial of service (memory corruption) and possibly execute arbitrary code by instantiating certain Visual Studio 6.0 ActiveX COM Objects in Internet Explorer, including (1) tcprops.dll, (2) fp30wec.dll, (3) mdt2db.dll, (4) mdt2qd.dll, and (5) vi30aut.dll.

Frequently asked questions

What is CVE-2006-4494?: Microsoft Visual Studio 6.0 allows remote attackers to cause a denial of service (memory corruption) and possibly execute arbitrary code by instantiating certain Visual Studio 6.0 ActiveX COM Objects in Internet Explorer, including (1) tcprops.dll, (2) fp30wec.dll, (3) mdt2db.dll, (4) mdt2qd.dll, and (5) vi30aut.dll.
How severe is CVE-2006-4494?: CVE-2006-4494 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2006-4494 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 22% (97th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2006-4494?: CVE-2006-4494 primarily affects Microsoft Visual Studio. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2006-4494?: 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-2006-4494 published?: CVE-2006-4494 was published on 2006-08-31 and last updated on 2026-06-16.

References

Affected products (2)

cpe:2.3:a:microsoft:visual_studio:6.0:*:*:*:*:*:*:*
cpe:2.3:a:microsoft:visual_studio:6.0:sp1:*:*:*:*:*:*

More vulnerabilities in Microsoft Visual Studio

CVE-2009-3126 — Critical (CVSS 9.3): Integer overflow in GDI+ in Microsoft Internet Explorer 6 SP1, Windows XP SP2 and SP3, Office XP SP3, Office 2003 SP3,…
CVE-2009-2528 — Critical (CVSS 9.3): GDI+ in Microsoft Office XP SP3 does not properly handle malformed objects in Office Art Property Tables, which allows…
CVE-2009-2504 — Critical (CVSS 9.3): Multiple integer overflows in unspecified APIs in GDI+ in Microsoft .NET Framework 1.1 SP1, .NET Framework 2.0 SP1 and…
CVE-2009-2503 — Critical (CVSS 9.3): GDI+ in Microsoft Internet Explorer 6 SP1, Windows XP SP2 and SP3, Windows Server 2003 SP2, Office XP SP3, Office 2003…
CVE-2009-2501 — Critical (CVSS 9.3): Heap-based buffer overflow in GDI+ in Microsoft Internet Explorer 6 SP1, Windows XP SP2 and SP3, Office XP SP3, Office…
CVE-2009-2500 — Critical (CVSS 9.3): Integer overflow in GDI+ in Microsoft Internet Explorer 6 SP1, Windows XP SP2 and SP3, Office XP SP3, Office 2003 SP3,…

All CVEs affecting Microsoft Visual Studio →