PatchSiren cyber security CVE debrief
CVE-2026-97766 Microsoft CVE debrief
Microsoft Office Excel Remote Code Execution Vulnerability allows an unauthorized attacker to execute code over a network due to a heap-based buffer overflow. This vulnerability affects Microsoft Office deployments, particularly those using Excel, and defenders should assess exposure and prioritize patching. The vulnerability has a high severity with a CVSS score of 8.8 and is classified as HIGH. The CVE record was published on 2026-10-13T19:00:36.956Z and has not been modified since then.
- Vendor
- Microsoft
- Product
- Microsoft 365 Apps for Enterprise
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-10-13
- Original CVE updated
- 2026-10-14
- Advisory published
- 2026-10-13
- Advisory updated
- 2026-10-14
Who should care
Defenders responsible for Microsoft Office deployments, particularly those using Excel, should assess exposure and prioritize patching. This includes reviewing compensating controls for exposed systems while remediation is scheduled and verified. Additionally, defenders should check relevant monitoring, detection, and logs for exposed assets that need extra review.
Why it matters
CVE-2026-97766 is a high-severity vulnerability in Microsoft Office Excel that allows remote code execution. Defenders should prioritize patching vulnerable versions and assess exposure across various deployment contexts.
- Potential code execution over a network
- Unauthorized access to sensitive data
- Disruption of business operations
- Need for patching and verification
Technical summary
A heap-based buffer overflow in Microsoft Office Excel allows an unauthorized attacker to execute code over a network. This vulnerability is classified as a remote code execution vulnerability and has a high severity with a CVSS score of 8.8. The affected product is Microsoft Office Excel, and defenders should prioritize patching vulnerable versions and assess exposure across various deployment contexts.
Defensive priority
Defenders should prioritize patching vulnerable Microsoft Office versions and assess exposure across various deployment contexts.
Recommended defensive actions
- Patch vulnerable Microsoft Office versions
- Assess exposure across various deployment contexts
- Verify inventory for affected products
- 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 inventory for affected products and monitor for suspicious activity. The official CVE Program record and NIST NVD detail page offer additional information. However, the current impact and potential code execution over a network require further assessment and patching of vulnerable Microsoft Office versions.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-97766 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-97766
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-97766 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-97766
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Microsoft Office Excel Remote Code Execution Vulnerability
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/97xxx/CVE-2026-97766.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-97766
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.