CVE-2026-97759 Microsoft CVE debrief

Who should care

Defenders responsible for Microsoft Office deployments should assess exposure and prioritize patching. They should also verify exposure in their environment and review 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-97759 is a high-severity vulnerability in Microsoft Office Excel that allows remote code execution. Defenders should prioritize patching vulnerable versions and verify exposure in their environment.

• Potential code execution over a network
• Requires patching of vulnerable Microsoft Office versions
• Verification of exposure in the environment is necessary

Technical summary

A use-after-free vulnerability in Microsoft Office Excel allows an unauthorized attacker to execute code over a network. This vulnerability affects Microsoft Office deployments and has a high severity score of 8.8. Defenders should prioritize patching vulnerable versions and verify exposure in their environment. The vulnerability is classified as HIGH and has a CVSS score of 8.8.

Defensive priority

Defenders should prioritize patching vulnerable Microsoft Office versions and verify exposure in their environment.

Recommended defensive actions

• Patch vulnerable Microsoft Office versions
• Verify exposure in the environment
• 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 their environment and prioritize patching vulnerable versions. The vulnerability has a high severity score of 8.8 and is classified as HIGH. There is no information available on known ransomware campaign use or vendor project.

Sources and references

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.