# CVE-2025-70795: Privilege escalation in n/a

> An admin-privileged user can exploit insufficient caller validation in the STProcessMonitor driver to terminate protected processes, causing denial of service.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 17 Apr 2026
- **Updated:** 17 Apr 2026
- **Also known as:** GHSA-42p2-73mx-2pch

## What is CVE-2025-70795?

CVE-2025-70795 is a medium-severity vulnerability in n/a, published on 17 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

STProcessMonitor 11.11.4.0, part of the Safetica Application suite, allows an admin-privileged user to send crafted IOCTL requests to terminate processes that are protected through a third-party implementation. This is caused by insufficient caller validation in the driver's IOCTL handler, enabling unauthorized processes to perform those actions in kernel space. Successful exploitation can lead to denial of service by disrupting critical third-party services or applications. Unauthorized processes load the driver and send a crafted IOCTL request (0xB822200C) to terminate processes protected by a third-party implementation. This action exploits insufficient caller validation in the driver's IOCTL handler, allowing unauthorized processes to perform termination operations in kernel space. Successful exploitation can lead to denial of service by disrupting critical third-party services or applications.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-70795?


## How do I fix CVE-2025-70795?

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

## Is CVE-2025-70795 being exploited?

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

Public exploit code:

- The PoC for CVE-2025-70795 / CVE-2026-0828 and updated driver (github_poc): https://github.com/ANYLNK/STProcessMonitorBYOVD

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-70795 and fix it if it is affected.

What it is: CVE-2025-70795 is a medium-severity vulnerability in n/a, published on 17 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-2025-70795 exists.

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-2025-70795/ (Markdown: https://insights.sbomify.com/CVE-2025-70795/index.md)
```

## Sources

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

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