# CVE-2026-102413: Uncaught Exception in Elastic Endpoint Leading to Denial of Service

> An attacker can cause a denial of service in Elastic Endpoint by triggering an unhandled exception via a crafted file name in specific locales.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-f8hp-h7qq-64mp, MINI-8xf8-h78v-qhgw, MINI-h935-74wr-j26x, MINI-xf5p-qc7x-r28r

## What is CVE-2026-102413?

CVE-2026-102413 is a medium-severity denial of service vulnerability in Elastic Agent and Elastic Defend, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-248 (Uncaught Exception)

## Which versions are affected by CVE-2026-102413?


## How do I fix CVE-2026-102413?

Apply the vendor's patch.

## Is CVE-2026-102413 being exploited?

There is no known exploitation of CVE-2026-102413 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102413 and fix it if it is affected.

What it is: CVE-2026-102413 is a medium-severity denial of service vulnerability in Elastic Agent and Elastic Defend, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102413 in the wild and no public exploit code.

Affected product: Elastic Agent and Elastic Defend. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102413/ (Markdown: https://insights.sbomify.com/CVE-2026-102413/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102413
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102413
- OSV: https://osv.dev/vulnerability/CVE-2026-102413

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102413/
Summaries are generated and may contain mistakes; the official description above is the record.