# CVE-2026-7279: eMPIA Technology｜AVACAST - DLL Hijacking

> Authenticated local attackers can execute arbitrary code with system privileges via DLL hijacking in AVACAST.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 28 Apr 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-m4rm-63h7-9mj5

## What is CVE-2026-7279?

CVE-2026-7279 is a high-severity vulnerability in eMPIA Technology AVACAST, published on 28 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

AVACAST developed by eMPIA Technology, has a DLL Hijacking vulnerability, allowing authenticated local attackers to place a malicious DLL in a specific directory, resulting in arbitrary code execution with system privileges when the system loads the DLL.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2026-7279 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7279 is a high-severity vulnerability in eMPIA Technology AVACAST, published on 28 Apr 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-7279 in the wild and no public exploit code.

Affected product: eMPIA Technology AVACAST. 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-7279/ (Markdown: https://insights.sbomify.com/CVE-2026-7279/index.md)
```

## Sources

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

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