# CVE-2016-20059: IObit Malware Fighter 4.3.1 Unquoted Service Path Privilege Escalation

> Local attackers can escalate privileges to LocalSystem by placing a malicious executable in the unquoted service path of IObit Malware Fighter.

- **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:** 4 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-rjmh-3x6m-hgvq

## What is CVE-2016-20059?

CVE-2016-20059 is a high-severity vulnerability in IObit Malware Fighter, published on 4 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

IObit Malware Fighter 4.3.1 contains an unquoted service path vulnerability in the IMFservice and LiveUpdateSvc services that allows local attackers to escalate privileges. Attackers can insert a malicious executable file in the unquoted service path and trigger privilege escalation when the service restarts or the system reboots, executing code with LocalSystem privileges.

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

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

It affects 1 product.


Products: Iobit Malware Fighter.

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

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

## Is CVE-2016-20059 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20059 exists.

## Other vulnerabilities in IObit Malware Fighter

- [CVE-2020-23864](https://insights.sbomify.com/CVE-2020-23864/): Privilege escalation in n/a (high 7.8)
- [CVE-2018-19084](https://insights.sbomify.com/CVE-2018-19084/): Memory corruption in n/a (high 7.8)
- [CVE-2018-19085](https://insights.sbomify.com/CVE-2018-19085/): Memory corruption in n/a (high 7.8)
- [CVE-2018-19086](https://insights.sbomify.com/CVE-2018-19086/): Memory corruption in n/a (high 7.8)
- [CVE-2018-19087](https://insights.sbomify.com/CVE-2018-19087/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-20059 is a high-severity vulnerability in IObit Malware Fighter, published on 4 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20059 exists.

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

## Sources

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

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