# CVE-2026-2998: eAI Technologies｜ERP - DLL Hijacking

> Authenticated local attackers can execute arbitrary code by placing a malicious DLL in the application directory.

- **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:** 23 Feb 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-hm88-j5r4-fwj3

## What is CVE-2026-2998?

CVE-2026-2998 is a high-severity code injection vulnerability in eAI Technologies ERP F2, published on 23 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ERP developed by eAI Technologies has a DLL Hijacking vulnerability, allowing authenticated local attackers to place a crafted DLL file in the same directory as the program, thereby executing arbitrary code.

Weakness: CWE-426 (Untrusted Search Path)

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


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

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

## Is CVE-2026-2998 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2998 is a high-severity code injection vulnerability in eAI Technologies ERP F2, published on 23 Feb 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-2998 in the wild and no public exploit code.

Affected product: eAI Technologies ERP F2. 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-2998/ (Markdown: https://insights.sbomify.com/CVE-2026-2998/index.md)
```

## Sources

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

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