# CVE-2025-69783: Security feature bypass in n/a

> A local attacker can bypass OpenEDR self-defense by spoofing trusted process names, enabling unauthorized driver interaction and potential privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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:** 17 Mar 2026
- **Also known as:** GHSA-3wp7-xc34-h3f8

## What is CVE-2025-69783?

CVE-2025-69783 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 attacker can bypass OpenEDR's 2.5.1.0 self-defense mechanism by renaming a malicious executable to match a trusted process name (e.g., csrss.exe, edrsvc.exe, edrcon.exe). This allows unauthorized interaction with the OpenEDR kernel driver, granting access to privileged functionality such as configuration changes, process monitoring, and IOCTL communication that should be restricted to trusted components. While this issue alone does not directly grant SYSTEM privileges, it breaks OpenEDR's trust model and enables further exploitation leading to full local privilege escalation.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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

It affects 1 product.


Products: Xcitium Openedr.

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

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

## Is CVE-2025-69783 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-69784](https://insights.sbomify.com/CVE-2025-69784/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69783 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: There is no known exploitation of CVE-2025-69783 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-2025-69783/ (Markdown: https://insights.sbomify.com/CVE-2025-69783/index.md)
```

## Sources

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

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