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

> A local attacker can exploit a kernel driver flaw to load malicious DLLs into high-privilege processes, achieving SYSTEM-level code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/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:** 16 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-7p63-78wp-5m6f

## What is CVE-2025-69784?

CVE-2025-69784 is a high-severity vulnerability in n/a, published on 16 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A local, non-privileged attacker can abuse a vulnerable IOCTL interface exposed by the OpenEDR 2.5.1.0 kernel driver to modify the DLL injection path used by the product. By redirecting this path to a user-writable location, an attacker can cause OpenEDR to load an attacker-controlled DLL into high-privilege processes. This results in arbitrary code execution with SYSTEM privileges, leading to full compromise of the affected system.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Xcitium Openedr.

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

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

## Is CVE-2025-69784 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-69783](https://insights.sbomify.com/CVE-2025-69783/): Security feature bypass in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69784 is a high-severity vulnerability in n/a, published on 16 Mar 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-69784 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-69784/ (Markdown: https://insights.sbomify.com/CVE-2025-69784/index.md)
```

## Sources

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

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