CVE-2015-6040

CVE-2015-6040 is a critical-severity vulnerability in Microsoft Excel with a CVSS 2.0 base score of 9.3. Its EPSS exploit-prediction score of 14% places it in the 96th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-119.

Key facts

Description

Microsoft Excel 2007 SP3, Excel 2010 SP2, Excel for Mac 2011, Excel 2016 for Mac, Office Compatibility Pack SP3, and Excel Viewer allow remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability."

Frequently asked questions

What is CVE-2015-6040?
Microsoft Excel 2007 SP3, Excel 2010 SP2, Excel for Mac 2011, Excel 2016 for Mac, Office Compatibility Pack SP3, and Excel Viewer allow remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability."
How severe is CVE-2015-6040?
CVE-2015-6040 has a CVSS 2.0 base score of 9.3, rated critical severity.
Is CVE-2015-6040 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 14% (96th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2015-6040?
CVE-2015-6040 primarily affects Microsoft Excel. In total, 7 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2015-6040?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2015-6040 published?
CVE-2015-6040 was published on 2015-12-09 and last updated on 2026-06-17.

References

Affected products (7)

More vulnerabilities in Microsoft Excel

All CVEs affecting Microsoft Excel →

Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities

Browse all CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities →