# CVE-2026-6424: Use-after-free vulnerability in ESET security products for Linux

> An attacker can trigger a kernel panic in ESET Linux security products via a use-after-free vulnerability, causing system denial of service.

- **Severity:** Medium 6.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-g4c4-fjm7-hv64

## What is CVE-2026-6424?

CVE-2026-6424 is a medium-severity use after free vulnerability in ESET, spol. s.r.o. ESET Endpoint Antivirus for Linux, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Use-after-free vulnerability in ESET Linux products potentially allowed an attacker to trigger kernel panic on the system

Weakness: CWE-416 (Use After Free)

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


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

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

## Is CVE-2026-6424 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6424 is a medium-severity use after free vulnerability in ESET, spol. s.r.o. ESET Endpoint Antivirus for Linux, published on 16 Jul 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-6424 in the wild and no public exploit code.

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

## Sources

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

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