Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-105598 Overview
CVE-2026-105598 is a heap-based buffer overflow [CWE-122] in Microsoft Office Access that allows an unauthorized attacker to execute arbitrary code over a network. The flaw affects Microsoft 365 Apps, Office 2021 LTSC, and Office 2024 LTSC on both x86 and x64 architectures. Exploitation requires user interaction, typically opening a crafted Access database file delivered through email or a web download. Successful exploitation yields code execution in the context of the current user, enabling full compromise of confidentiality, integrity, and availability on the host.
Critical Impact
Remote attackers can achieve arbitrary code execution on systems running affected Microsoft Office Access versions when a user opens a malicious file.
Affected Products
- Microsoft 365 Apps (Enterprise, x86 and x64)
- Microsoft Office 2021 LTSC (x86 and x64)
- Microsoft Office 2024 LTSC (x86 and x64)
Discovery Timeline
- 2026-10-13 - CVE-2026-105598 published to NVD
- 2026-10-15 - Last updated in NVD database
Technical Details for CVE-2026-105598
Vulnerability Analysis
The vulnerability is a heap-based buffer overflow in Microsoft Office Access. Microsoft classifies the issue under [CWE-122], indicating that an operation writes beyond the bounds of a buffer allocated on the heap. The flaw is reachable through the Access file parsing path, where attacker-controlled content in a database file triggers an out-of-bounds write on the heap. Overwriting adjacent heap metadata or object pointers enables an attacker to redirect execution and run arbitrary code in the context of the Office process. Attack delivery is network-based, but exploitation requires the victim to open the crafted file. Refer to the Microsoft CVE-2026-105598 Update Guide for authoritative product details.
Root Cause
The root cause is improper validation of size or length values when Access allocates and populates a heap buffer during file parsing. When attacker-supplied field data exceeds the allocated region, the write operation corrupts adjacent heap memory. This corruption can be shaped to overwrite function pointers, virtual table entries, or allocator metadata, enabling control-flow hijacking.
Attack Vector
The attack vector is network-based with required user interaction. An attacker crafts a malicious Access database file and delivers it through phishing email, a web link, a file share, or a collaboration platform. When the user opens the file in a vulnerable Access client, parsing triggers the heap overflow. No prior authentication to the target is required, and successful exploitation inherits the user's privileges, which may include access to local files, credentials, and network resources.
No public proof-of-concept exploit code is available at the time of publication, and this CVE is not listed in the CISA Known Exploited Vulnerabilities catalog.
Detection Methods for CVE-2026-105598
Indicators of Compromise
- Microsoft Access process (MSACCESS.EXE) spawning command interpreters such as cmd.exe, powershell.exe, or wscript.exe.
- Unexpected child processes or outbound network connections initiated by Access shortly after a user opens an .accdb, .mdb, or .accde file.
- Access databases arriving from untrusted email senders, external file shares, or links to recently registered domains.
- Crash events or Windows Error Reporting entries referencing MSACCESS.EXE with access violation signatures consistent with heap corruption.
Detection Strategies
- Hunt for process-lineage anomalies where MSACCESS.EXE is the parent of script interpreters, LOLBins, or memory-injection tooling.
- Alert on Office applications writing executable content (.exe, .dll, .hta, .js) to disk, especially in user profile or temp directories.
- Correlate Access file-open events with subsequent outbound connections to uncategorized or newly observed domains.
Monitoring Recommendations
- Enable Microsoft Defender attack surface reduction rules that block Office child processes and executable content creation.
- Ingest Office telemetry and endpoint process events into a centralized SIEM for retroactive hunting across all Office hosts.
- Monitor email gateways for inbound Access database attachments and flag or sandbox-detonate them before delivery.
How to Mitigate CVE-2026-105598
Immediate Actions Required
- Apply the Microsoft security update referenced in the Microsoft CVE-2026-105598 Update Guide across all affected Microsoft 365 Apps, Office 2021 LTSC, and Office 2024 LTSC installations.
- Prioritize patching for users who routinely receive external files, including finance, legal, HR, and executive assistants.
- Verify that Microsoft 365 Apps update channels are configured to deliver security updates on a timely cadence.
Patch Information
Microsoft has published the fix through the Microsoft Security Response Center. Administrators should consult the Microsoft CVE-2026-105598 Update Guide for the specific build numbers that resolve the heap overflow in Microsoft 365 Apps and Office 2021/2024 LTSC channels. Deploy updates through Microsoft Update, WSUS, Intune, or Configuration Manager according to your patch management workflow.
Workarounds
- Block inbound Access database file types (.accdb, .mdb, .accde, .mde) at email gateways and secure web gateways when business workflows allow.
- Enforce Protected View and Office File Block policies for Access files originating from the internet or untrusted locations.
- Enable Microsoft Defender attack surface reduction rules to prevent Office applications from launching child processes.
- Restrict macro execution and Access runtime use to signed, trusted sources through Group Policy.
# Configuration example: enable ASR rule to block Office child processes
Set-MpPreference -AttackSurfaceReductionRules_Ids d4f940ab-401b-4efc-aadc-ad5f3c50688a `
-AttackSurfaceReductionRules_Actions Enabled
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

