# CVE-2025-50892: Missing authorization in n/a

> A local attacker can exploit improper privilege validation in the EaseUS Todo Backup driver to read/write raw disk data, causing information disclosure, denial of service, or 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:** 10 Sep 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-ch4p-cwc6-298r

## What is CVE-2025-50892?

CVE-2025-50892 is a high-severity missing authorization vulnerability in n/a, published on 10 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The eudskacs.sys driver version 20250328 shipped with EaseUs Todo Backup 1.2.0.1 fails to properly validate privileges for I/O requests (IRP_MJ_READ/IRP_MJ_WRITE) sent to its device object. This allows a local, low-privileged attacker to perform arbitrary raw disk reads and writes, leading to sensitive information disclosure, denial of service, or local privilege escalation.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Easeus Eudskacs.sys Driver.

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

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

## Is CVE-2025-50892 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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