CVE-2015-1641
Exploitation confirmed. First attested on 2021-11-03 by CISA-ADP, CISA KEV, GCVE · kevintel.
- Published2015-04-14
- WeaknessCWE-787
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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."
Timeline
dates in UTC- 2015-04-1420:59CVE publishedNVD
- 2021-11-03Listed as exploited by GCVEGCVE
- 2021-11-03Exploitation first reportedCISA KEV
- 2021-11-03Added to the CISA KEV catalogCISA KEV
- 2025-02-1019:34SSVC exploitation set to activeCISA-ADP
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2015-1641?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2015-1641?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2007.x | = 2007 | no fix published | NVD |
| 2010.x | = 2010 | no fix published | NVD |
| 2011.x | = 2011 | no fix published | NVD |
| 2013.x | = 2013 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2010.x | = 2010 | no fix published | NVD |
| 2013.x | = 2013 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2010.x | = 2010 | no fix published | NVD |
| 2013.x | = 2013 | no fix published | NVD |
3 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- CISA’s required action: Apply updates per vendor instructions.due 2022-05-03
Advisories and patches
- docs.microsoft.comPatch · Vendor Advisory
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
CISA Known Exploited Vulnerability
- Date Added
- 2021-11-03
- Patch Due Date
- 2022-05-03
- Ransomware Use
- Unknown
- Required Action
- Apply updates per vendor instructions.
Sources
- CISA KEVKEV entry2021-11-03
- GCVEexploitation2021-11-03
- CISA-ADPSSVC decisionactive2025-02-10
- OpenCVESSVC decisionactive—
- CISA-ADPCVSS 3.17.82025-02-10
- NVDCVSS 3.17.8read 2026-10-23
- NVDCVSS 2.09.3read 2026-10-23
- CISA-ADPweakness (CWE)CWE-7872025-02-10
- NVDweakness (CWE)CWE-787read 2026-10-23
- FIRST EPSSEPSS score97.2 %read 2026-10-23
- PoC-in-GitHubproof of concept1read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- Published
- 2015-04-14
- Last Modified
- 2026-06-17
- NVD status
- Analyzed
Frequently asked questions
What is CVE-2015-1641?
Is CVE-2015-1641 actively exploited?
What is the CVSS score for CVE-2015-1641?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- For a threat intelligence platform: malware, C2 and ransomware indicators over STIX/TAXII.
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.