CVE-2026-58618
Received Received - Intake

BaseFortify

Vulnerability report for CVE-2026-58618, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-14

Last updated on: 2026-07-14

Assigner: Microsoft Corporation

Description

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

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-14
Last Modified
2026-07-14
Generated
2026-07-14
AI Q&A
2026-07-14
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
microsoft office_excel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-122 A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-58618 is a heap-based buffer overflow vulnerability in Microsoft Office Excel. This flaw allows an unauthorized attacker to execute arbitrary code on a victim's system.

A heap-based buffer overflow occurs when a program writes more data to a buffer than it can hold, corrupting memory in the heap. In this case, the vulnerability is triggered in Excel, enabling an attacker to run malicious code locally on the affected system.

  • The CVSS v3.1 base score for this vulnerability is 7.8, indicating a high severity level.
  • The attack vector is local (AV:L), meaning the attacker must have access to the victim's system or trick the user into opening a malicious file.
  • The vulnerability does not require elevated privileges (PR:N) but does require user interaction (UI:R), such as opening a specially crafted Excel file.
Impact Analysis

This vulnerability can have severe consequences if exploited successfully.

  • An attacker could execute arbitrary code on your system, potentially gaining full control over it.
  • This could lead to data theft, including sensitive personal or corporate information stored on the system.
  • The attacker could install malware, ransomware, or backdoors, allowing persistent access to your system.
  • Exploitation could result in system crashes, data corruption, or unauthorized modifications to files.

Since the vulnerability requires user interaction (e.g., opening a malicious Excel file), the risk increases if users are not cautious about the files they open.

Compliance Impact

This vulnerability could impact compliance with several common standards and regulations, depending on the context of its exploitation.

  • GDPR (General Data Protection Regulation): If the vulnerability leads to unauthorized access or theft of personal data, it could result in a data breach. Organizations may face fines, legal action, or reputational damage for failing to protect personal data as required by GDPR.
  • HIPAA (Health Insurance Portability and Accountability Act): If the affected system contains protected health information (PHI), exploitation of this vulnerability could lead to a breach of PHI. This would require notification and could result in penalties for non-compliance with HIPAA security rules.
  • Other standards like PCI DSS (Payment Card Industry Data Security Standard) could also be impacted if the vulnerability exposes payment card data or systems processing such data.

Organizations should assess the potential impact of this vulnerability on their compliance posture and take appropriate measures to mitigate the risk, such as applying patches or implementing compensating controls.

Detection Guidance

The provided context does not include specific detection methods or commands for identifying the presence of CVE-2026-58618 on a network or system.

To detect this vulnerability, you may need to rely on Microsoft-provided tools or updates. Typically, Microsoft releases security updates and detection guidance through their official channels, such as the Microsoft Security Response Center (MSRC) or Windows Update.

You can check for installed updates on Windows systems using the following command in PowerShell or Command Prompt:

  • wmic qfe list | find "KBNumber" (replace KBNumber with the relevant update identifier if available)
  • Get-HotFix -Id KBNumber (PowerShell alternative)

For Excel-specific detection, you may need to verify the installed version of Microsoft Office Excel and compare it against the patched versions listed in Microsoft's advisory.

Mitigation Strategies

Based on the provided context, the following immediate steps are recommended to mitigate CVE-2026-58618:

  • Apply the latest security updates from Microsoft as soon as they are available. This vulnerability is addressed by Microsoft through their update mechanism.
  • Restrict access to Microsoft Office Excel files from untrusted sources. Avoid opening Excel files received via email or downloaded from the internet unless they are verified as safe.
  • Use Microsoft Defender or other endpoint protection tools to monitor for suspicious activity related to Excel or Office applications.
  • Enable attack surface reduction rules in Microsoft Defender to block potentially malicious behaviors associated with Office applications.
  • Monitor Microsoft's official advisory for additional guidance or workarounds if updates are not immediately available.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-58618. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart