PatchSiren cyber security CVE debrief
CVE-2026-97012 Microsoft CVE debrief
A stack-based buffer overflow in Microsoft Office Outlook allows an unauthorized attacker to execute code over a network. This CVE record was published on 2026-10-13T19:00:35.758Z and has not been modified since then. The NVD entry is currently unclassified. The vulnerability affects Microsoft 365 Apps for Enterprise, Microsoft Office LTSC 2021, and Microsoft Office LTSC 2024. Defenders should assess exposure and prioritize patching or workarounds for these affected products. The vulnerability is a remote code execution vulnerability, which can allow an attacker to execute code on the affected system.
- 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 Outlook deployments should assess exposure and prioritize patching or workarounds. This includes IT administrators, security teams, and vulnerability management teams. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. They should also plan vendor-supported updates or mitigations through normal change控制,
Why it matters
Defenders should prioritize verifying exposure of Microsoft Office Outlook and assessing the need for patches or workarounds due to a stack-based buffer overflow vulnerability allowing remote code execution.
- Potential remote code execution
- Need for patching or workarounds
- Monitoring for exploitation attempts
Technical summary
A stack-based buffer overflow in Microsoft Office Outlook allows an unauthorized attacker to execute code over a network. The vulnerability affects Microsoft 365 Apps for Enterprise, Microsoft Office LTSC 2021, and Microsoft Office LTSC 2024. The vulnerability is a remote code execution vulnerability, which can allow an attacker to execute code on the affected system. Defenders should prioritize verifying exposure of Microsoft Office Outlook and assessing the need for patches or workarounds.
Defensive priority
Defenders should prioritize verifying exposure of Microsoft Office Outlook and assessing the need for patches or workarounds.
Recommended defensive actions
- Verify exposure of Microsoft Office Outlook
- Assess the need for patches or workarounds
- Monitor for potential exploitation attempts
Evidence notes
The CVE record and source item provide details on the vulnerability, but additional information on exploitation or impact is limited. There is no evidence of exploitation in the wild, but defenders should verify exposure of Microsoft Office Outlook and assess the need for patches or workarounds. The source item provides details on the vulnerability, but the impact and exploitation are not well understood. The CVE Program record and NVD detail page provide additional context on the CVE.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-97012 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-97012
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-97012 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-97012
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Microsoft Office Outlook Remote Code Execution Vulnerability
Unverified legacy reference
URL: https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/97xxx/CVE-2026-97012.json
cve_program_cvelist_v5
-
Source reference
Unverified legacy reference
URL: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-97012
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.