# CVE-2026-28760: Other in RATOC RAID Monitoring Manager for Windows

> Attackers can execute arbitrary code with administrator privileges by placing a malicious DLL in the installer's directory.

- **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Mar 2026
- **Updated:** 26 Mar 2026
- **Also known as:** GHSA-c8rm-hg85-p336

## What is CVE-2026-28760?

CVE-2026-28760 is a high-severity vulnerability in RATOC RAID Monitoring Manager for Windows, published on 26 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The installer of RATOC RAID Monitoring Manager for Windows searches the current directory to load certain DLLs. If a user is directed to place a crafted DLL with the installer, an arbitrary code may be executed with the administrator privilege.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2026-28760?


## How do I fix CVE-2026-28760?

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

## Is CVE-2026-28760 being exploited?

There is no known exploitation of CVE-2026-28760 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-28760 and fix it if it is affected.

What it is: CVE-2026-28760 is a high-severity vulnerability in RATOC RAID Monitoring Manager for Windows, published on 26 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-28760 in the wild and no public exploit code.

Affected product: RATOC RAID Monitoring Manager for Windows. 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-2026-28760/ (Markdown: https://insights.sbomify.com/CVE-2026-28760/index.md)
```

## Sources

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

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