CVE-2026-69442: Microsoft Office heap-based buffer overflow

CVE-2026-69442 · Severity: high · CVSS 8.8 · Published 2026-09-08

Microsoft Office contains a heap-based buffer overflow vulnerability that allows attackers to execute arbitrary code on affected systems over the network. An attacker could exploit this flaw to gain unauthorized access to sensitive documents and data, install malware, or compromise business operations without requiring user interaction or valid credentials.

Technologies: Microsoft Office. Vendors: Microsoft.

Quick answers

Is CVE-2026-69442 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-69442 being exploited in the wild.
How severe is CVE-2026-69442?
High severity, with a CVSS score of 8.8, published 8 September 2026.
Which products and versions are affected?
Microsoft Office.
Is there a fix for CVE-2026-69442?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-69442 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-69442?
Check whether you run Microsoft Office. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A heap-based buffer overflow exists in Microsoft Office that can be exploited over the network to achieve remote code execution. The vulnerability stems from improper bounds checking in memory allocation, allowing an attacker to write data beyond allocated heap buffers. The attack vector is network-based with no authentication or user interaction required. A successful exploit would grant the attacker the ability to execute arbitrary code with the privileges of the Office application. Patch availability status is unknown from the provided references; consult Microsoft Security Response Center for current remediation guidance.

Affected products

  • Microsoft Office

Timeline

  • 2026-09-08: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.