dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2026-32680

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 →
80/100
Remediation priority · High
Zero-click

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 allows to customize the installation folder. If the installation folder is customized to some non-default one, the folder may be left with un-secure ACLs and non-administrative users can alter contents of that folder. It may allow a non-administrative user to execute an arbitrary code with SYSTEM 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 · moderate confidence

The RATOC RAID Monitoring Manager installer for Windows creates installation directories with overly permissive Access Control Lists (ACLs) when users specify a custom installation path rather than the default. This allows non-privileged users to modify, replace, or inject files (executables or DLLs) within that directory. When the application or a related service runs with elevated privileges, the attacker-controlled code executes with SYSTEM-level permissions, enabling full system compromise.

MitigationAfter installation, manually audit and harden ACLs on the installation folder to restrict write access to Administrators only; use the default Program Files location when possible, or deploy via enterprise tools that enforce secure permissions during installation.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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. Locate RATOC RAID Monitoring Manager installation
    Check for the product in Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall; alternatively, search for "RATOC RAID" or "RATOC" folders in common installation locations like C:\Program Files\, C:\Program Files (x86)\, or other custom paths
    Affected if The product is found installed on the system
  2. Identify the installation directory path
    Review the registry entry (InstallLocation value) from the uninstall registration, or right-click the application shortcut and select Properties to view the target path
    Affected if The installation path is a custom directory outside the default Program Files location
  3. Verify directory ownership and permissions
    Right-click the installation folder in Windows Explorer, select Properties, then the Security tab; click Advanced to view detailed permissions; check if Users or authenticated users have Write, Modify, or Full Control permissions
    Affected if Non-privileged users (Users group, Authenticated Users) have Write, Modify, or Full Control permissions on the directory
  4. Confirm service or scheduled task runs with elevated privileges
    Open Services.msc and look for RATOC-related services; check Task Scheduler for RATOC tasks; note if they run under SYSTEM, LocalSystem, or an admin account
    Affected if A RATOC service or scheduled task runs under SYSTEM, LocalSystem, or another privileged account

A user is affected if RATOC RAID Monitoring Manager is installed to a custom path and that directory grants non-privileged users write or modify permissions, allowing file injection that could be executed with SYSTEM-level 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

After installation, manually audit and harden ACLs on the installation folder to restrict write access to Administrators only; use the default Program Files location when possible, or deploy via enterprise tools that enforce secure permissions during installation.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32680 — 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-32680 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