PatchSiren cyber security CVE debrief
CVE-2026-66807 Microsoft CVE debrief
A stack-based buffer overflow in the Microsoft Office Graphics Component could allow an unauthorized attacker to execute code locally. This vulnerability affects multiple Microsoft Office products and versions. The CVE record was published on 2026-08-11T17:07:02.683Z and has not been modified since then. The NVD entry is currently High. Defenders and IT administrators responsible for managing Microsoft Office installations should assess exposure and prioritize patching vulnerable systems. The vulnerability has a high severity score and could have significant impacts if exploited.
- 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 IT administrators responsible for managing Microsoft Office installations should assess exposure and prioritize patching vulnerable systems.
Why it matters
CVE-2026-66807 is a high-severity vulnerability in the Microsoft Office Graphics Component that could allow local code execution by an unauthorized attacker. Defenders should prioritize patching vulnerable systems, especially in environments where local code execution could have significant impacts. The vulnerability affects multiple Microsoft Office products and versions, and Microsoft has provided patches for affected systems.
- Potential for local code execution by unauthorized attackers
- Possible disruption to business operations if exploited
- Need for defenders to verify and apply patches to vulnerable systems
- Importance of inventory management to identify and remediate affected software instances
Technical summary
A stack-based buffer overflow in the Microsoft Office Graphics Component could allow an unauthorized attacker to execute code locally. The vulnerability affects multiple Microsoft Office products, including Microsoft 365 Apps for Enterprise, Microsoft Office 2019, Microsoft Office 365 for Mac, and others.
Defensive priority
Defenders should prioritize patching vulnerable Microsoft Office installations, especially in environments where local code execution could have significant impacts.
Recommended defensive actions
- Patch vulnerable Microsoft Office installations
- Verify and apply updates for Microsoft 365 Apps for Enterprise, Microsoft Office 2019, Microsoft Office 365 for Mac, and other affected products
- Review and update inventory to ensure all instances of affected software are identified and remediated
Evidence notes
The CVE Program record and NVD vulnerability detail provide information on the vulnerability. Microsoft's official advisory is referenced, indicating a patch is available.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-66807 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-66807
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-66807 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-66807
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Microsoft Office Graphics Component Remote Code Execution Vulnerability
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/66xxx/CVE-2026-66807.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-66807
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.