PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-64911 Microsoft CVE debrief

Microsoft Office Remote Code Execution Vulnerability allows an unauthorized attacker to execute code locally due to an integer overflow or wraparound in Microsoft Office. This vulnerability poses a significant risk to Microsoft Office installations, as it could allow attackers to gain unauthorized access and execute malicious code. Defenders and administrators should assess exposure and apply the patch to prevent potential attacks. The vulnerability is caused by an integer overflow or wraparound in Microsoft Office, which can be exploited by an unauthorized attacker to execute code locally.

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 and administrators responsible for Microsoft Office installations should assess exposure and apply the patch to prevent potential attacks. They should also inventory and monitor Microsoft Office installations for potential vulnerability and assess and mitigate risks associated with unauthorized code execution.

Why it matters

The vulnerability allows an unauthorized attacker to execute code locally, posing a significant risk to Microsoft Office installations. Defenders and administrators should assess exposure and apply the patch.

  • Verify and apply patches for Microsoft Office to prevent local code execution
  • Inventory and monitor Microsoft Office installations for potential vulnerability
  • Assess and mitigate risks associated with unauthorized code execution

Technical summary

The vulnerability is caused by an integer overflow or wraparound in Microsoft Office, allowing an unauthorized attacker to execute code locally. This vulnerability affects Microsoft Office installations and poses a significant risk to defenders and administrators. The vulnerability can be exploited by an unauthorized attacker to execute malicious code, making it essential for defenders and administrators to assess exposure and apply the patch.

Defensive priority

High

Recommended defensive actions

  • Review and apply the Microsoft patch for the vulnerability
  • Inventory Microsoft Office installations to identify potentially affected systems
  • Monitor for suspicious activity related to the vulnerability

Evidence notes

The CVE record and NVD vulnerability detail provide information on the vulnerability. Microsoft has released a patch for the vulnerability. The vulnerability allows an unauthorized attacker to execute code locally, posing a significant risk to Microsoft Office installations. Defenders and administrators should assess exposure and apply the patch. The CVE record was published on 2026-08-11T17:06:42.620Z and has not been modified since then. There is no information on known or unknown R

Sources and references

Verified primary and authoritative sources

  • CVE-2026-64911 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-64911 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

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

Supplemental references

  • Microsoft Office Remote Code Execution Vulnerability

    Unverified legacy reference

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

    cve_program_cvelist_v5

  • Source reference

    Unverified legacy reference

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

    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.