dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2026-28760

HIGH · 7.8 CVSS v3.0 Published 2026-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The RATOC RAID Monitoring Manager Windows installer is vulnerable to DLL hijacking due to insecure DLL search path ordering. The installer searches the current working directory for DLLs before checking system directories, allowing an attacker to place a malicious DLL that gets loaded and executed with administrator privileges when the installer runs.

MitigationUsers should only download installers from official verified sources. The vendor should rebuild the installer using safe DLL loading practices (e.g., SetDllDirectory, absolute paths, or manifest-based binding) and digitally sign the updated installer.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if RATOC RAID Monitoring Manager is installed
    Open Programs and Features (appwiz.cpl) or check for the installation directory (commonly under C:\Program Files\RATOC or similar). Look for an entry named RATOC RAID Monitoring Manager or RATOC RMM.
    Affected if The product is listed in installed programs or its installation directory exists on the system.
  2. Determine the installed version
    Right-click the application in Programs and Features and select Properties, then check the Version field. Alternatively, locate the main executable (often named something like RMM.exe or raidman.exe) in the installation folder, right-click it, and view its file version properties.
    Affected if The detected version falls within the vulnerable range (compare your version to any official vendor release notes for this CVE; if uncertain, assume the installer version used is potentially affected).
  3. Identify if the vulnerable installer was ever run
    Review system logs: open Event Viewer, navigate to Windows Logs > Application, and filter for events around the time of initial installation. Look for entries from the RATOC installer (often named something like raidman_setup.exe or similar). Also check the user account that performed the installation.
    Affected if The installer was executed on the system and the current working directory at that time was writable by an untrusted user, or the installer was run from a location like a network share or downloaded folder.
  4. Check for suspicious DLLs in installer location
    If you have the original installer file, inspect the directory where it was run from. Look for any unexpected DLL files (e.g., version.dll, d3d9.dll, winhttp.dll) that are not part of the legitimate installer package.
    Affected if Unexpected DLL files are present in the same folder as the installer or were present at the time of installation.
  5. Review installed DLLs for anomalies
    Use a tool like Process Explorer or examine the installation directory for DLLs that may have been dropped during installation. Compare the DLLs present against those expected from a clean install of the same version.
    Affected if Extra or unexpected DLL files exist in the installation directory that were not part of the official installer package.

A user is affected if they have run the RATOC RAID Monitoring Manager installer from a directory where an attacker could have placed a malicious DLL, and the installer successfully loaded a DLL from that location with administrator privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should only download installers from official verified sources. The vendor should rebuild the installer using safe DLL loading practices (e.g., SetDllDirectory, absolute paths, or manifest-based binding) and digitally sign the updated installer.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28760 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28760 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data