{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-69783 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-69783 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2025-69783 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2025-69783 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-69783/ (Markdown: https://insights.sbomify.com/CVE-2025-69783/index.md)","id":"CVE-2025-69783","markdown":"https://insights.sbomify.com/CVE-2025-69783/index.md","name":"CVE-2025-69783","record":{"aliases":["GHSA-3wp7-xc34-h3f8"],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["privilege_escalation","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OpenEDR kernel driver","requires_auth":"low_privilege","summary":"A local attacker can bypass OpenEDR self-defense by spoofing trusted process names, enabling unauthorized driver interaction and potential privilege escalation.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"openedr","vendor":"xcitium"}],"cvss":{"score":7.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-250","name":"Execution with Unnecessary Privileges"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2025-69783","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2025-69784"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-69771"},"products":["n/a"],"published":"2026-03-16","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2025-69784","kev_date_added":null,"published":"2026-03-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-17","vendors":["n/a"]},"summary":"A local attacker can bypass OpenEDR self-defense by spoofing trusted process names, enabling unauthorized driver interaction and potential privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-69783/"}