What is the CVSS score of CVE-2026-44824?

CVE-2026-44824 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Microsoft Office are affected by CVE-2026-44824?

A heap-overflow vulnerability in Microsoft Office (CVE-2026-44824, CVSS 7.8) enables local code execution when users open malicious documents, with no public exploit identified at time of analysis.. A patch is available.

How to fix or mitigate CVE-2026-44824?

Within 24 hours: Issue urgent security alert to all Office users; prohibit opening documents from untrusted sources; coordinate with IT to identify and test file sandboxing or validation capabilities. Within 7 days: Disable Office document preview features where feasible; implement network controls to restrict document origins; document all compensating controls deployed. Within 30 days: Establish monitoring cadence for Microsoft security advisories; track patch availability timelines; conduct assessment of document handling practices across business units.

Microsoft Office CVE-2026-44824

EUVD-2026-35666 HIGH

Heap-based Buffer Overflow (CWE-122)

2026-06-09 secure@microsoft.com

GHSA-xhmf-jjc9-v9vr

Heap Overflow Microsoft Buffer Overflow 365 Apps Microsoft 365 Office 2016 Office 2019 Office 2021 Office 2024 Sharepoint Server

7.8

CVSS 3.1 · Vendor: microsoft

Temporal: 6.8

Severity by source

Vendor (microsoft) PRIMARY

7.8 HIGH

AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

ENISA EUVD

HIGH

qualitative

CIRCL (temporal)

6.8 MEDIUM

cvss

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch available

Jun 09, 2026 - 19:03 EUVD

Analysis Generated

Jun 09, 2026 - 18:28 vuln.today

CVE Published

Jun 09, 2026 - 17:17 nvd

HIGH 7.8

DescriptionCVE.org

Heap-based buffer overflow in Microsoft Office allows an unauthorized attacker to execute code locally.

AnalysisAI

Local code execution in Microsoft Office is possible through a heap-based buffer overflow (CWE-122) that triggers when a user opens or previews a maliciously crafted document. The CVSS 7.8 score reflects local attack vector with required user interaction, and no public exploit identified at time of analysis. Successful exploitation yields full confidentiality, integrity, and availability impact in the context of the current user.

Technical ContextAI

The flaw is a heap-based buffer overflow (CWE-122) inside Microsoft Office's document parsing or rendering code paths. Heap overflows occur when code writes past the bounds of a dynamically allocated buffer, corrupting adjacent heap metadata or object pointers; in modern Office this is typically reached through malformed structures inside OOXML, RTF, or legacy binary formats (e.g., crafted records, embedded objects, or font/image streams) processed by Office's parsers. Exact affected SKUs and builds are not enumerated in the provided NVD data - no CPE strings were supplied - and resolution depends on the Microsoft Security Update Guide entry referenced for the CVE.

RemediationAI

Apply the Microsoft security update referenced in the MSRC advisory (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-44824) on Patch Tuesday cadence; exact fixed build numbers are not included in the NVD data and must be read from the MSRC guide per Office channel (Current Channel, Monthly Enterprise, Semi-Annual, LTSC, Office for Mac). No vendor-released patch version was provided in this dataset, so verify the update KB matches your deployed Click-to-Run or MSI channel. Until patched, compensating controls include enabling Protected View and Application Guard for Office, blocking inbound Office documents from untrusted senders at the mail gateway, disabling the Outlook Reading/Preview Pane for high-risk mailboxes (trade-off: reduces triage speed), and applying Attack Surface Reduction rules such as 'Block Office applications from creating child processes' and 'Block executable content from email client and webmail' (trade-off: may break legitimate macro-driven workflows).