High

CVE-2015-0085 — Use-after-free vulnerability in Microsoft Office 2007 SP3, Excel 2007 SP3, PowerPoint 2007 SP3,...

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."

Published Mar 11, 2015 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: microsoft

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 18.7% (30-day exploitation probability)+15
Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

18.75%

ahead of 97% of scored CVEs · Oct 14, 2026

Affects

Microsoft

Excel and 10 more

CVSS base

9.3

High · 1 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Microsoft Excel, Microsoft Excel Viewer, Microsoft Microsoft SharePoint Foundation…).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Microsoft	Excel	version 2007-sp3version 2010-sp2	Vulnerable	NIST National Vulnerability Database
Microsoft	Excel Viewer	versions not specified by the source	Vulnerable	NIST National Vulnerability Database
Microsoft	Microsoft SharePoint Foundation	version 2013-sp1version 2013version 2010-sp2	Vulnerable	NIST National Vulnerability Database
Microsoft	Office	version 2010-sp2version 2013-sp1version 2013	Vulnerable	NIST National Vulnerability Database
Microsoft	Office Compatibility Pack	versions not specified by the source	Vulnerable	NIST National Vulnerability Database
Microsoft	Office Web Apps Server	version 2013-sp1version 2013version 2010-sp2	Vulnerable	NIST National Vulnerability Database
Microsoft	Powerpoint	version 2007-sp3version 2010-sp2	Vulnerable	NIST National Vulnerability Database
Microsoft	Sharepoint Server	version 2010-sp2version 2013-sp1version 2013version 2007-sp3	Vulnerable	NIST National Vulnerability Database
Microsoft	Sharepoint Services	version 3.0-sp3	Vulnerable	NIST National Vulnerability Database
Microsoft	Web Applications	version 2010-sp2	Vulnerable	NIST National Vulnerability Database
Microsoft	Word	version 2013version 2013-sp1version 2010-sp2version 2007-sp3	Vulnerable	NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Medium

Authentication

None

Confidentiality

Complete

Integrity

Complete

Availability

Complete

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
9.3	CVSS 2.0	High	8.6	10.0	nvd@nist.gov via NIST National Vulnerability Database

AV:N/AC:M/Au:N/C:C/I:C/A:C (score shown at the top: nvd@nist.gov)

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
SSVC assessment updated
Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 14, 2026
Affected products added · microsoft/excel, microsoft/excel viewer, microsoft/office, microsoft/office compatibility pack, microsoft/office web app
Oct 14, 2026 · NIST National Vulnerability Database
CVSS changed · 9.3
Oct 14, 2026 · NIST National Vulnerability Database
Source status changed · → Modified
Oct 14, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 14, 2026 · Alertas do Telegram
2015
CVE published
Mar 11, 2015 · microsoft

Source activity

Repeated readings are counted rather than listed.

2× References added · Oct 14, 2026 – Oct 14, 2026
1× Official description updated · Oct 14, 2026 – Oct 14, 2026

References

4 on the record

github.com/advisories/GHSA-p6v9-v6m6-gqv6
GitHub Security Advisories
www.securitytracker.com/id/1031896
vdb-entry, x_refsource_SECTRACK, NIST National Vulnerability Database
docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-022
vendor-advisory, x_refsource_MS, NIST National Vulnerability Database
nvd.nist.gov/vuln/detail/CVE-2015-0085
GitHub Security Advisories

Elsewhere on this site

Microsoft
every CVE for this vendor

Related CVEs (same products)

Medium CVE-2026-97783 Microsoft Office SharePoint Spoofing Vulnerability 2d
Medium CVE-2026-97782 Microsoft Office SharePoint Tampering Vulnerability 2d
High CVE-2026-97755 Microsoft Office Excel Remote Code Execution Vulnerability 2d
High CVE-2026-96044 Microsoft Office SharePoint Elevation of Privilege Vulnerability 2d
Medium CVE-2026-88209 Microsoft Office SharePoint Spoofing Vulnerability 2d
High CVE-2026-88204 Microsoft Office SharePoint Spoofing Vulnerability 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No CWE classification.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2015-0085 is "Use-after-free vulnerability in Microsoft Office 2007 SP3, Excel 2007 SP3, PowerPoint 2007 SP3,...", rated High. It affects Excel (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.3 describes technical severity. EPSS 18.75% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.