# CVE-2026-36425: Privilege escalation in n/a

> Local attackers can escalate privileges by sending unauthorized process termination requests to the OPSWAT AppRemover driver via an insecure IOCTL handler.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A: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 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-gf97-46vm-gc57

## What is CVE-2026-36425?

CVE-2026-36425 is a medium-severity vulnerability in n/a, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue in OPSWAT AppRemover Driver (ardrv.sys) v2017.10.02.1551 and earlier in IOCTL handler 0x2420031. Any local user can open the device and send process termination requests without privilege validation.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-36425 being exploited?

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

Public exploit code:

- CVE-2026-36425 OPSWAT AppRemover (ardrv.sys) improper access control advisory (github_poc): https://github.com/redteamfortress/CVE-2026-36425
- Use cve-2026-36425 killer edr，360 can killer (github_poc): https://github.com/gongchuang1089/EDRKiller

## Fix prompt for AI coding agents

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

What it is: CVE-2026-36425 is a medium-severity vulnerability in n/a, published on 16 Jul 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-36425 in the wild and no public exploit code.

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

## Sources

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

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