CVE-2025-47169 Details
Description
Heap-based buffer overflow in Microsoft Office Word allows an unauthorized attacker to execute code locally.
A heap-based buffer overflow vulnerability has been identified in Microsoft Office Word. This issue allows an unauthorized attacker to execute code locally. The vulnerability requires user interaction, as an attacker must send a malicious file that the user needs to open.
Users can apply the security update for this vulnerability, which is available through the Microsoft Update Catalog. For Microsoft 365 Apps for Enterprise, the security update will be released as soon as possible, and customers will be notified via a revision to this CVE information.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jun 11, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-47169 | [email protected] | Broken Link |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-122 | Heap-based Buffer Overflow | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| microsoft 365 apps | All versions |
CPE
Remediation
| |
| microsoft office | 2019 |
CPE
Remediation
| |
| microsoft office long term servicing channel | 2021 2024 |
CPE
Remediation
| |
| microsoft sharepoint enterprise server | 2016 |
CPE
Remediation
| |
| microsoft sharepoint server | 2019 |
CPE
Remediation
| |
| microsoft word | 2016 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Jul 9, 2025 | Initial Analysis | [email protected] |
| Jun 10, 2025 | New CVE Received | [email protected] |