# CVE-2025-10541: Local Privilege Escalation via Insecure Update Mechanism in iMonitor EAM

> Local attackers can escalate privileges to SYSTEM by placing malicious files in a world-writable update directory used by the iMonitor EAM service.

- **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:** 25 Sep 2025
- **Updated:** 3 Nov 2025
- **Also known as:** GHSA-mw5x-5ggx-p642

## What is CVE-2025-10541?

CVE-2025-10541 is a high-severity vulnerability in iMonitor EAM, published on 25 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

iMonitor EAM 9.6394 installs a system service (eamusbsrv64.exe) that runs with NT AUTHORITY\SYSTEM privileges. This service includes an insecure update mechanism that automatically loads files placed in the C:\sysupdate\ directory during startup. Because any local user can create and write to this directory, an attacker can place malicious DLLs or executables in it. Upon service restart, the files are moved to the application’s installation path and executed with SYSTEM privileges, leading to privilege escalation.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

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

## Is CVE-2025-10541 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10541 is a high-severity vulnerability in iMonitor EAM, published on 25 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-10541 exists.

Affected product: iMonitor EAM. 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-10541/ (Markdown: https://insights.sbomify.com/CVE-2025-10541/index.md)
```

## Sources

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

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