# CVE-2026-42936: Other in HYPER SBI 2

> A DLL hijacking vulnerability in the HYPER SBI 2 installer allows arbitrary code execution if a malicious DLL is present in the execution directory.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-j386-q724-3f5c

## What is CVE-2026-42936?

CVE-2026-42936 is a high-severity vulnerability in HYPER SBI 2, published on 15 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The installer of HYPER SBI 2 insecurely loads Dynamic Link Libraries. If there is a crafted DLL at the same directory when invoking the affected installer, arbitrary code may be executed with the privilege of the user invoking the installer.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2026-42936 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42936 is a high-severity vulnerability in HYPER SBI 2, published on 15 Jul 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-42936 in the wild and no public exploit code.

Affected product: HYPER SBI 2. 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-42936/ (Markdown: https://insights.sbomify.com/CVE-2026-42936/index.md)
```

## Sources

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

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