# CVE-2026-84408: Privilege escalation in QND Advance

> Local attackers can execute arbitrary commands with SYSTEM privileges via improper access control in a named pipe.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-4388-7v5g-7q9g

## What is CVE-2026-84408?

CVE-2026-84408 is a high-severity vulnerability in QualitySoft Corporation QND Advance, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

QND contains an improper access control vulnerability in a named pipe, which may allow a local attacker who is logged in to a Windows PC where the affected product's client is installed to execute arbitrary commands with SYSTEM privileges.

Weakness: CWE-782 (Exposed IOCTL with Insufficient Access Control)

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


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

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

## Is CVE-2026-84408 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84408 is a high-severity vulnerability in QualitySoft Corporation QND Advance, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-84408 in the wild and no public exploit code.

Affected product: QualitySoft Corporation QND Advance. 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-84408/ (Markdown: https://insights.sbomify.com/CVE-2026-84408/index.md)
```

## Sources

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

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