# CVE-2026-9169: LUCID Vision Labs: DLL Search Order Hijacking in Arena SDK 1.0.80.49 on Windows

> Local attackers can execute arbitrary code by placing malicious DLLs in PATH directories, affecting LUCID Vision Labs Arena SDK users.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-rchh-68vw-685q

## What is CVE-2026-9169?

CVE-2026-9169 is a high-severity code injection vulnerability in LUCID Vision Labs Arena SDK, published on 7 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DLL Search Order Hijacking in LUCID Vision Labs Arena SDK 1.0.80.49 on Windows allows a local attacker to execute arbitrary code with the privileges of the application by placing a malicious DLL in a user-controlled directory listed in the PATH environment variable, which the SDK traverses when a required dependency is not found locally.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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


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

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

## Is CVE-2026-9169 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9169 is a high-severity code injection vulnerability in LUCID Vision Labs Arena SDK, published on 7 Aug 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-9169 in the wild and no public exploit code.

Affected product: LUCID Vision Labs Arena SDK. 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-9169/ (Markdown: https://insights.sbomify.com/CVE-2026-9169/index.md)
```

## Sources

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

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