VulnerabilityPublished 16 Mar 2026Updated 17 Mar 2026

CVE-2025-69783: openedr · CVE-2025-69783 is a local privilege escalation

Affects openedrSource CVE Database V5

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.8High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubcomodosecurity/openedr`pkg:github/comodosecurity/openedr`Other threats	Affected =2.5.1.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

2) Implement strict local access controls and limit user permissions to reduce the risk of local attackers executing renamed malicious binaries. 3) Employ application whitelisting and process integrity verification tools to detect and prevent execution of renamed or spoofed executables mimicking trusted processes. 4) Monitor kernel driver interactions and IOCTL communications for anomalous behavior indicative of exploitation attempts. 5) Use endpoint detection rules to alert on processes with suspicious names or unexpected privilege escalations. 6) Conduct regular audits of endpoint security agents to ensure their integrity and configuration have not been tampered with. 7) Educate system administrators and security teams about this vulnerability to recognize potential exploitation signs. 8) Consider deploying additional layered security controls such as behavior-based detection and network segmentation to limit the impact of a compromised endpoint. These steps go beyond generic advice by focusing on detection of process impersonation and restricting local attack vectors.

Description

CVE-2025-69783 is a local privilege escalation vulnerability in OpenEDR version 2.5.1.0 where an attacker can bypass the product's self-defense mechanism by renaming a malicious executable to mimic trusted process names such as csrss.exe, edrsvc.exe, or edrcon.exe. This bypass allows unauthorized interaction with the OpenEDR kernel driver, granting access to privileged functions including configuration changes, process monitoring, and IOCTL communication. Although this vulnerability does not directly provide SYSTEM privileges, it undermines the trust model of OpenEDR and can be leveraged for further exploitation leading to full local privilege escalation. The vulnerability has a CVSS score of 7.

Impact

The impact of CVE-2025-69783 is substantial for organizations deploying OpenEDR 2.5.1.0 as part of their endpoint security infrastructure. By bypassing the self-defense mechanism, attackers can manipulate the security agent's kernel driver, potentially disabling or altering security monitoring and response capabilities. This undermines the integrity and reliability of endpoint detection, allowing attackers to conceal malicious activities, escalate privileges, and move laterally within networks. The vulnerability could lead to unauthorized configuration changes, process tampering, and execution of privileged commands, severely compromising endpoint security. In environments where OpenEDR is a critical security control, exploitation could facilitate advanced persistent threats (APTs) and insider attacks. The lack of direct SYSTEM privilege escalation means initial exploitation requires local access, but the subsequent privilege escalation chain could lead to full system compromise. This poses a risk to confidentiality, integrity, and availability of organizational assets, especially in sectors with high security requirements.

CWE-250Execution with Unnecessary Privileges (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
Architecture and Design · Separation of Privilege
Identify the functionality that requires additional privileges, such as access to privileged operating system resources. Wrap and centralize this functionality if possible, and isolate the privileged code as much as possible from other code.
Architecture and Design · Attack Surface Reduction
Identify the functionality that requires additional privileges, such as access to privileged operating system resources. Wrap and centralize this functionality if possible, and isolate the privileged code as much as possible from other code.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Vulnerable Dependency Management (opens in a new tab)
OWASP ASVS 4.0.3
V1.14.5 (opens in a new tab)
V1.2.1 (opens in a new tab)
V14.2.6 (opens in a new tab)
Attack patterns
Cross Zone Scripting (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
Target Programs with Elevated Privileges (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Mar 2026, 01:05 UTC

WeaknessesCWE-250

Technical details

References

Community reviews

Related threats