Skip to main content

Severity by source

Vendor (microsoft) PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
ENISA EUVD
HIGH
qualitative
vuln.today AI
5.5 MEDIUM

Local file-parse trigger with mandatory user interaction; no auth needed to open a file; confidentiality-only impact consistent with out-of-bounds read memory disclosure.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
Analysis Generated
Jul 22, 2026 - 16:42 vuln.today
CVE Published
Jul 14, 2026 - 17:08 cve.org
MEDIUM 5.5

DescriptionCVE.org

Out-of-bounds read in Microsoft Office allows an unauthorized attacker to disclose information locally.

AnalysisAI

Out-of-bounds read (CWE-125) in Microsoft Office's file parsing logic exposes potentially sensitive in-memory data to a local attacker when a victim opens a specially crafted document, affecting Windows and macOS Office editions as well as Microsoft SharePoint Server. The CVSS 5.5 Medium score reflects a local-only attack vector with mandatory user interaction, confining impact to information disclosure with no integrity or availability consequence. No public exploit code exists, CISA SSVC classifies exploitation as 'none' with no automation potential, and the EPSS of 0.51% (40th percentile) confirms low current exploitation probability.

Technical ContextAI

CWE-125 (Out-of-bounds Read) describes a memory safety flaw where a program reads data beyond the boundary of an allocated buffer, potentially revealing adjacent memory contents such as heap data, stack frames, or neighboring object fields. The flaw resides in Microsoft Office's document parsing subsystem - a broad attack surface common to file-format processing in Word, Excel, PowerPoint, and SharePoint document libraries. CPE strings confirm impact across cpe:2.3:a:microsoft:microsoft_office_2016, cpe:2.3:a:microsoft:microsoft_office_2019, cpe:2.3:a:microsoft:microsoft_office_ltsc_2021, cpe:2.3:a:microsoft:microsoft_office_ltsc_2024, cpe:2.3:a:microsoft:microsoft_365_apps_for_enterprise, cpe:2.3:a:microsoft:microsoft_office_365_for_mac, cpe:2.3:a:microsoft:microsoft_office_ltsc_for_mac_2021, cpe:2.3:a:microsoft:microsoft_office_ltsc_for_mac_2024, cpe:2.3:a:microsoft:microsoft_sharepoint_enterprise_server_2016, and cpe:2.3:a:microsoft:microsoft_sharepoint_server_2019. The inclusion of SharePoint suggests the parser vulnerability may be triggered server-side via document upload or preview workflows, though the AV:L vendor scoring implies the primary exploitation path is local file opening.

RemediationAI

Apply Microsoft's released patches for all affected products as the primary fix. For SharePoint Enterprise Server 2016, update to build 16.0.5561.1001 or later. For SharePoint Server 2019, update to 16.0.10417.20175 or later. For SharePoint Server Subscription Edition, update to 16.0.19725.20434 or later. For macOS editions (Office 365 for Mac, Office LTSC for Mac 2021, and Office LTSC for Mac 2024), update to build 16.111.26071215 or later. For all Windows Office editions (2016, 2019, LTSC 2021, LTSC 2024, and Microsoft 365 Apps for Enterprise), apply the updates available via https://aka.ms/OfficeSecurityReleases. The full Microsoft Security Response Center advisory is at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55023. Where immediate patching is not possible, configuring Office Protected View to prevent automatic processing of externally received files reduces exposure by requiring an additional user step before the vulnerable parser is invoked - note this does not block exploitation if users click through Protected View warnings. Restricting SharePoint document upload permissions for untrusted users is a targeted compensating control for the server-side attack surface.

CVE-2026-55033 HIGH
7.8 Jul 14

Local code execution in Microsoft Word (and Office/SharePoint components that render Word content) stems from an integer

CVE-2026-55038 HIGH
7.8 Jul 14

Arbitrary code execution in Microsoft Office Word (and the broader Office/365/SharePoint family) arises from a stack-bas

CVE-2026-55132 HIGH
7.8 Jul 14

Local code execution in Microsoft Word (part of Microsoft 365 Apps, Office 2019, Office LTSC 2021/2024, and Office for M

CVE-2026-55120 HIGH
7.8 Jul 14

Arbitrary code execution in Microsoft PowerPoint (and the broader Microsoft Office/365 suite on Windows and macOS) arise

CVE-2026-55123 HIGH
7.8 Jul 14

Local code execution in Microsoft Office PowerPoint (including Microsoft 365 Apps, Office 2019, Office LTSC 2021/2024, a

CVE-2026-55043 HIGH
7.8 Jul 14

Local code execution in Microsoft Office PowerPoint (CWE-122 heap-based buffer overflow) lets an unauthorized attacker r

CVE-2026-55127 HIGH
7.8 Jul 14

Local code execution in Microsoft Word (and the wider Microsoft Office / Microsoft 365 Apps family) lets an unauthorized

CVE-2026-55130 HIGH
7.8 Jul 14

Local code execution in Microsoft Word (Office 2016/2019, Microsoft 365 Apps, Office LTSC 2021/2024) arises from a heap-

CVE-2026-55128 HIGH
7.8 Jul 14

Local code execution in Microsoft Office Word (CWE-416 use-after-free) allows an unauthorized attacker to run arbitrary

CVE-2026-55134 HIGH
7.8 Jul 14

Local code execution in Microsoft Office Word (Microsoft 365 Apps, Office 2019/LTSC 2021/2024, Word 2016, and the macOS

CVE-2026-55055 HIGH
7.8 Jul 14

Local code execution in Microsoft Office Word (via a stack-based buffer overflow, CWE-121) lets an attacker run arbitrar

CVE-2026-55032 HIGH
7.8 Jul 14

Local code execution in Microsoft Office Word (across Microsoft 365 Apps, Office 2019/LTSC 2021/2024, Office for Mac, an

Share

CVE-2026-55023 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy