# CVE-2016-20092: NetDrive 2.6.12 Unquoted Service Path Elevation of Privilege

> Local attackers can execute arbitrary code with SYSTEM privileges by exploiting an unquoted service path in NetDrive.

- **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:** 19 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-4vvh-93ff-2f2v

## What is CVE-2016-20092?

CVE-2016-20092 is a high-severity vulnerability in NetDrive, published on 19 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NetDrive 2.6.12 contains an unquoted service path vulnerability in the Netdrive2_Service_Netdrive2 service that allows local users to execute arbitrary code with SYSTEM privileges. Attackers can insert malicious executables in the system root path that will be executed during service startup or system reboot, resulting in privilege escalation.

Weakness: CWE-428 (Unquoted Search Path or Element)

## Which versions are affected by CVE-2016-20092?


## How do I fix CVE-2016-20092?

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

## Is CVE-2016-20092 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20092 and fix it if it is affected.

What it is: CVE-2016-20092 is a high-severity vulnerability in NetDrive, published on 19 Jun 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-2016-20092 in the wild and no public exploit code.

Affected product: NetDrive. 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-2016-20092/ (Markdown: https://insights.sbomify.com/CVE-2016-20092/index.md)
```

## Sources

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

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