# CVE-2026-30896: Other in Qsee Client

> Attackers can execute arbitrary code with administrative privileges by tricking users into running a Qsee Client installer with a malicious DLL in the same 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:** 9 Mar 2026
- **Updated:** 9 Mar 2026
- **Also known as:** GHSA-gww4-6rrf-6f3g

## What is CVE-2026-30896?

CVE-2026-30896 is a high-severity vulnerability in Qsee Client, published on 9 Mar 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 for Qsee Client versions 1.0.1 and prior insecurely load Dynamic Link Libraries (DLLs). When a user is directed to place some malicious DLL to the same directory and execute the affected installer, then arbitrary code may be executed with the administrative privilege.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Q-See Qsee Client.

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

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

## Is CVE-2026-30896 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-30896 is a high-severity vulnerability in Qsee Client, published on 9 Mar 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-30896 in the wild and no public exploit code.

Affected product: Qsee Client. 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-30896/ (Markdown: https://insights.sbomify.com/CVE-2026-30896/index.md)
```

## Sources

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

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