Skip to main content
VulnerabilityPublished

CVE-2026-32680: RATOC RAID Monitoring Manager for Windows · Incorrect Default Permissions

Affects RATOC RAID Monitoring Manager for WindowsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.0 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
RATOC Systems, Inc.RATOC RAID Monitoring Manager for WindowsAffected
  • =prior to 2.00.009.260220
Fixed in–

AI-suggested

  1. Upgrade RATOC RAID Monitoring Manager to version 2.00.009.260220 or later, where the issue is resolved.
  2. If upgrading is not immediately possible, verify and manually correct the ACLs on the installation folder, especially if a non-default path was used, ensuring only administrative users have write permissions.
  3. Restrict local user permissions on systems running the software to minimize the risk of unauthorized access.
  4. Implement strict application whitelisting and endpoint protection to detect and prevent unauthorized code execution.
  5. Regularly audit file and folder permissions on critical software installations to detect misconfigurations.
  6. Employ least privilege principles for user accounts to reduce the impact of potential privilege escalation.
  7. Monitor system logs for unusual activities indicative of privilege escalation attempts.
  8. Educate system administrators about the risks of customizing installation paths without verifying security settings. These steps go beyond generic advice by focusing on permission auditing and administrative awareness specific to this vulnerability scenario.

Description

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.

References

Community reviews

Loading reviews…