# CVE-2015-0085: Use after free in n/a

> Remote attackers can execute arbitrary code by tricking users into opening a crafted Office document, affecting multiple Office and SharePoint versions.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Mar 2015
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-p6v9-v6m6-gqv6

## What is CVE-2015-0085?

CVE-2015-0085 is a critical use after free vulnerability in Microsoft Excel, published on 11 Mar 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Use-after-free vulnerability in Microsoft Office 2007 SP3, Excel 2007 SP3, PowerPoint 2007 SP3, Word 2007 SP3, Office 2010 SP2, Excel 2010 SP2, PowerPoint 2010 SP2, Word 2010 SP2, Office 2013 Gold and SP1, Word 2013 Gold and SP1, Office 2013 RT Gold and SP1, Word 2013 RT Gold and SP1, Excel Viewer, Office Compatibility Pack SP3, Word Automation Services on SharePoint Server 2010 SP2, Excel Services on SharePoint Server 2013 Gold and SP1, Word Automation Services on SharePoint Server 2013 Gold and SP1, Web Applications 2010 SP2, Office Web Apps Server 2010 SP2, Web Apps Server 2013 Gold and SP1, SharePoint Server 2007 SP3, Windows SharePoint Services 3.0 SP3, SharePoint Foundation 2010 SP2, SharePoint Server 2010 SP2, SharePoint Foundation 2013 Gold and SP1, and SharePoint Server 2013 Gold and SP1 allows remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Component Use After Free Vulnerability."

## Which versions are affected by CVE-2015-0085?

It affects 11 products.


Products: Microsoft Excel, Microsoft Excel Viewer, Microsoft Office, Microsoft Office Compatibility Pack, Microsoft Office Web Apps Server, Microsoft Powerpoint, Microsoft Sharepoint Foundation, Microsoft Sharepoint Server, Microsoft Sharepoint Services, Microsoft Web Applications, Microsoft Word.

## How do I fix CVE-2015-0085?

No fix has been published for CVE-2015-0085 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-0085 being exploited?

There is no known exploitation of CVE-2015-0085 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Excel

- [CVE-2019-1297](https://insights.sbomify.com/CVE-2019-1297/): Microsoft Excel Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2009-0238](https://insights.sbomify.com/CVE-2009-0238/): Microsoft Office Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2016-7262](https://insights.sbomify.com/CVE-2016-7262/): Microsoft Office Security Feature Bypass (high 7.8, exploited in the wild)
- [CVE-2009-3129](https://insights.sbomify.com/CVE-2009-3129/): Microsoft Excel Featheader Record Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2008-0081](https://insights.sbomify.com/CVE-2008-0081/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-0085 and fix it if it is affected.

What it is: CVE-2015-0085 is a critical use after free vulnerability in Microsoft Excel, published on 11 Mar 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-0085 in the wild and no public exploit code.

Affected product: Microsoft Excel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-0085/ (Markdown: https://insights.sbomify.com/CVE-2015-0085/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-0085
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-0085
- OSV: https://osv.dev/vulnerability/CVE-2015-0085

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-0085/
Summaries are generated and may contain mistakes; the official description above is the record.