CVE-2026-102413: Uncaught Exception in Elastic Endpoint Leading to Denial of Service
Uncaught Exception (CWE-248) in Elastic Endpoint can lead to denial of service via a specially crafted file name. When Elastic Defend's Elastic Endpoint component processes a file name under certain system locale configurations (including Chinese, Japanese, and Korean locales) on Windows, an unhandled exception can occur during file-path handling. This causes the Elastic Endpoint process to crash and restart repeatedly, which can degrade or disable Elastic Defend's real-time malware prevention and behavioral detection capabilities on the affected host for as long as the condition persists.
Affected Software
Event History
Frequently Asked Questions
Which systems are exposed to this issue?
Windows hosts running Elastic Defend's Elastic Endpoint component are affected when they use certain system locale configurations, including Chinese, Japanese, or Korean locales.
What does exploitation require?
The issue is triggered when Elastic Endpoint processes a specially crafted file name. The provided vector is local, and no privileges or user interaction are required according to the supplied severity vector.
What is the operational impact on an affected host?
Elastic Endpoint can crash and repeatedly restart while the triggering condition persists. This can degrade or disable Elastic Defend real-time malware prevention and behavioral detection on that host.