Privileged driver access via process-name spoofing
Published Mar 16, 2026 · Updated Mar 16, 2026
Privilege-boundary bypass in Xcitium OpenEDR 2.5.1.0 allows local users to access restricted kernel-driver functions. The isCurProcessTrusted check trusts a process when its path contains csrss.exe, edrsvc.exe, or edrcon.exe rather than validating its identity. Low-privileged local execution is required; the flaw permits configuration and monitoring changes but needs another flaw for SYSTEM access.
Summary
What happened
Privilege-boundary bypass in Xcitium OpenEDR 2.5.1.0 allows local users to access restricted kernel-driver functions. The isCurProcessTrusted check trusts a process when its path contains csrss.exe, edrsvc.exe, or edrcon.exe rather than validating its identity. Low-privileged local execution is required; the flaw permits configuration and monitoring changes but needs another flaw for SYSTEM access.
The record
- CVE
- CVE-2025-69783
- Published
- Mar 16, 2026
- Updated
- Mar 16, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-250, T1036
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 16, 2026CVE publishedPublication date reported by the CVE source.
- Mar 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- openedr_lpe.cppfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo