How severe is CVE-2015-1641?

CVE-2015-1641 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2015-1641?

CVE-2015-1641 affects the following products: microsoft office, microsoft office compatibility pack, microsoft office web apps, microsoft outlook, microsoft sharepoint server, microsoft word.

How do I patch CVE-2015-1641?

No patch has shipped for CVE-2015-1641 yet — track the microsoft office advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2015-1641 across my infrastructure?

Inventory every microsoft office deployment and check each version against the affected-products list above.

How do I mitigate CVE-2015-1641 if there is no patch (or I can't update yet)?

Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2015-1641 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2015-1641, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2015-1641?

CVE-2015-1641 has an EPSS (Exploit Prediction Scoring System) score of 97.2%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2015-1641 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2015-1641 (Microsoft Office Memory Corruption Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2015-1641?

CVE-2015-1641 is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2015-1641?

CVE-2015-1641 affects microsoft office (1 version, e.g. 2010); microsoft office compatibility pack; microsoft office web apps (2 versions, e.g. 2010, 2013); microsoft outlook (1 version, e.g. 2011), and 2 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2015-1641 published, and has it been updated?

CVE-2015-1641 was published on April 14, 2015 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2015-1641 — OFFICE

HIGH

CVE-2015-1641 is a high-severity (CVSS 7.8) Out-of-bounds Write vulnerability in microsoft office. It is in CISA's Known Exploited Vulnerabilities catalog (added 2021-11-03) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, Word 2013 RT SP1, Word for Mac 2011, Office Compatibility Pack SP3, Word Automation Services on SharePoint Server…

Published

Apr 14, 2015

Updated

Jun 17, 2026

Affected

6 products

Patched

See advisory

Exploits

4 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2021-11-03. Federal agencies were required to remediate by 2022-05-03.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2015-1641.

EPSS Exploitation Probability

via FIRST.org ↗

97.2%probability of exploitation in next 30 days

Very High Risk+0.55%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2015-1641 by exploitation likelihood (EPSS) against impact (CVSS). In the shaded patch-first corner (EPSS 50%+, CVSS 7.0+).

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the ≥ 90% band (highlighted). Counts from FIRST.org, log-scaled.

Description

Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, Word 2013 RT SP1, Word for Mac 2011, Office Compatibility Pack SP3, Word Automation Services on SharePoint Server 2010 SP2 and 2013 SP1, and Office Web Apps Server 2010 SP2 and 2013 SP1 allow remote attackers to execute arbitrary code via a crafted RTF document, aka "Microsoft Office Memory Corruption Vulnerability."

Affected Products

6 products · 12 configurations

Application

officemicrosoft

1 version

2010

Application

office compatibility packmicrosoft

all

Application

office web appsmicrosoft

2 versions

20102013

Application

outlookmicrosoft

1 version

2011

Application

sharepoint servermicrosoft

2 versions

20102013

Application

wordmicrosoft

4 versions

2007201020112013

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, …

docs.microsoft.comGoogle-sheetApr 2015

Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, …

github.comGithubOct 2015

Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, …

cisa.govCISAJul 2021

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every microsoft office deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2015-1641 yet — track the microsoft office advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2015-1641 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works

CVSS Score

7.8/10CVSS v3 base

Vector breakdown

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CWE Classification

CWE-787Out-of-bounds Write

Weaponization

No known public exploit tooling found.

Timeline

First exploit

Apr 14, 2015

Disclosed

Apr 14, 2015

KEV added

Nov 3, 2021

Last updated

Jun 17, 2026

Identifiers

CVE-2015-1641

References

Advisorysecurityfocus.com Advisorysecuritytracker.com Advisorysecurityfocus.com Advisorysecuritytracker.com Fixdocs.microsoft.com Fixdocs.microsoft.com Webcisa.gov

Related vulnerabilities

This CVE is high severity; 8 of 8 other CVEs with CWE-787 are rated as high or higher (top: critical).

CVE-2026-112398GHSA-78g4-xqwv-q3g8CVE-2026-96778CVE-2026-96639CVE-2026-63209CVE-2026-112397CVE-2026-70197CVE-2026-96233Browse all CWE-787

Provenance

Sources

OSV.devNVDCISA KEVFIRST.org (EPSS)

Last verifiedJun 17, 2026

CVE-2015-1641 — OFFICE

Exploitation Status

Actively exploited in the wild

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2015-1641 being exploited in your environment?