PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-58651 Microsoft CVE debrief

Microsoft Word Remote Code Execution Vulnerability allows an unauthorized attacker to execute code locally due to a heap-based buffer overflow in Microsoft Office Word. This vulnerability impacts Microsoft Office deployments, and defenders should assess exposure and apply patches from Microsoft. The CVE record and source item provide details on the vulnerability, but limited information is available on exploitation or impact. Defenders should prioritize verifying exposure in Microsoft Office deployments and applying patches from Microsoft.

Vendor
Microsoft
Product
Microsoft 365 Apps for Enterprise
CVSS
HIGH 7.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-11
Original CVE updated
2026-10-08
Advisory published
2026-08-11
Advisory updated
2026-10-08

Who should care

Defenders responsible for Microsoft Office deployments should assess exposure and apply patches from Microsoft. This vulnerability impacts Microsoft Office deployments, and defenders should prioritize verifying exposure and applying patches. Defenders should also monitor for suspicious activity and review compensating controls for exposed systems while remediation is scheduled and verified.

Why it matters

CVE-2026-58651 allows an unauthorized attacker to execute code locally via a heap-based buffer overflow in Microsoft Office Word. Defenders should prioritize verifying exposure in Microsoft Office deployments and applying patches from Microsoft.

  • Verify exposure in Microsoft Office Word deployments
  • Apply patches to prevent local code execution
  • Monitor for suspicious activity

Technical summary

A heap-based buffer overflow in Microsoft Office Word allows an unauthorized attacker to execute code locally. This vulnerability impacts Microsoft Office deployments, and defenders should assess exposure and apply patches from Microsoft. The vulnerability is a remote code execution vulnerability in Microsoft Word, and it is essential for defenders to prioritize verifying exposure in Microsoft Office deployments and applying patches from Microsoft.

Defensive priority

Defenders should prioritize verifying exposure in Microsoft Office deployments and applying patches from Microsoft.

Recommended defensive actions

  • Verify Microsoft Office Word deployments for exposure
  • Apply patches from Microsoft
  • Monitor for suspicious activity

Evidence notes

The CVE record and source item provide details on the vulnerability, but limited information is available on exploitation or impact. Defenders should verify exposure in Microsoft Office deployments and apply patches from Microsoft. The vulnerability allows an unauthorized attacker to execute code locally via a heap-based buffer overflow in Microsoft Office Word. Limited information is available on the vulnerability's impact, and defenders should exercise caution when assessing exposure

Sources and references

Verified primary and authoritative sources

  • CVE-2026-58651 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-58651

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-58651 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-58651

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Microsoft Word Remote Code Execution Vulnerability

    Unverified legacy reference

    URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/58xxx/CVE-2026-58651.json

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

    URL: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-58651

    Supplemental source - vendor-advisory, patch

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.