# CVE-2024-11859: DLL Search Order Hijacking in ESET products for Windows

> An attacker with administrator privileges can execute arbitrary code via DLL search order hijacking in ESET Windows products.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2025
- **Updated:** 16 Apr 2025
- **Also known as:** GHSA-w85p-m37q-fvfw

## What is CVE-2024-11859?

CVE-2024-11859 is a high-severity vulnerability in ESET, spol. s r.o. ESET Endpoint Antivirus for Windows, published on 7 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DLL Search Order Hijacking vulnerability potentially allowed an attacker with administrator privileges to load a malicious dynamic-link library and execute its code.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2024-11859?


## How do I fix CVE-2024-11859?

No fix has been published for CVE-2024-11859 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11859 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11859 and fix it if it is affected.

What it is: CVE-2024-11859 is a high-severity vulnerability in ESET, spol. s r.o. ESET Endpoint Antivirus for Windows, published on 7 Apr 2025. 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-2024-11859 in the wild and no public exploit code.

Affected product: ESET, spol. s r.o. ESET Endpoint Antivirus for Windows. 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-2024-11859/ (Markdown: https://insights.sbomify.com/CVE-2024-11859/index.md)
```

## Sources

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

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