Skip to main content
Mallory
CriticalVulnerability

CVE-2008-0112: Excel File Import Vulnerability (CVE-2008-0112)

Published Mar 11, 2008 · 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
EPSS32.2%98th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Microsoft Corporation
IdentifiersCVE-2008-0112CWE-94 · Improper Control of Generation of…

An unspecified vulnerability exists in Microsoft Excel 2000 SP3 and Office for Mac 2004 and 2008, where improper handling of crafted .SLK (Symbolic Link) files during import can allow user-assisted remote attackers to execute arbitrary code. The vulnerability is triggered when a user opens a maliciously crafted .SLK file, leading to code execution within the context of the user.

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 on the target system with the privileges of the user running Excel. This can lead to full compromise of the affected system if the user has administrative privileges.

Mitigation

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

Users should avoid opening .SLK files from untrusted sources. Email and web gateway filtering can be used to block or warn about .SLK file attachments. Running Office applications with least privilege and enabling security features such as Protected View can reduce risk.

Remediation

Patch, then assume compromise.

Apply the security updates provided by Microsoft that address this vulnerability. Users should ensure their Office installations are fully patched according to the latest security bulletins.

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 CorporationExcelapplication
Microsoft CorporationMicrosoft Officeapplication
FAQ

Frequently asked questions

Is CVE-2008-0112 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2008-0112 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2008-0112?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2008-0112. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2008-0112?
Apply the security updates provided by Microsoft that address this vulnerability. Users should ensure their Office installations are fully patched according to the latest security bulletins.
What products are affected by CVE-2008-0112?
Microsoft Corporation Excel and Microsoft Corporation Microsoft Office.
How severe is CVE-2008-0112?
CVE-2008-0112 has a CVSS v2 score of 9.3 (Critical) and an EPSS score of 32.2% (98th 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.