CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2026-67247 remediation guide

ASUSTOR Inc. ADM, data master

A path traversal vulnerability was found in the IHM Log handling of ADM. The vulnerability occurs because user-controlled disk serial input is not sufficiently validated before being used to construct the path of an IHM log database file. An authenticated attacker can exploit this issue to cause the affected component to access an unintended filesystem path or log database file. Affected products and versions include: from ADM 4.1.0 through ADM 4.3.3.RUN1 as well as from ADM 5.0.0 through ADM 5.1.3.RI81.

Open CVE record
ProductASUSTOR Inc. ADM, data master
Affected versions>= 5.0.0 <= 5.1.3.RI81, >= 4.1.0 <= 4.3.3.RUN1, >= 4.1.0.rhu2 <= 4.3.3.run1, >= 5.0.0.ra82 < 5.1.4.rjv2
Fixed versions5.1.4.rjv2
Priority basisReview · CVSS 7.1 · EPSS -
01

Identify the affected asset

Confirm whether ASUSTOR Inc. ADM, data master is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 5.0.0 <= 5.1.3.RI81, >= 4.1.0 <= 4.3.3.RUN1, >= 4.1.0.rhu2 <= 4.3.3.run1, >= 5.0.0.ra82 < 5.1.4.rjv2. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 5.1.4.rjv2. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.