Cyber Resilience

CVE-2026-18187

Asustor Data Master 4.1.0.rhu2 – 4.3.3.run1

Published
30 July 2026
Modified
04 August 2026
Patch / advisory
CVSS Score v4 7.1
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0027 18th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-18187 is a high-severity Use of Externally-Controlled Format String (CWE-134) vulnerability in Asustor Data Master. Its CVSS base score is 7.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

A format string vulnerability was found in the Internal Backup on the ADM. The vulnerability occurs because user-controlled task input may be included in an error response and processed through an unsafe format string operation. An authenticated attacker can exploit…

more

this issue to disclose memory information or cause denial of service of the affected CGI process. 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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-67244Same product: Asustor Data Master
CVE-2026-18186Same product: Asustor Data Master
CVE-2026-18188Same product: Asustor Data Master
CVE-2026-6643Same product: Asustor Data Master
CVE-2026-67248Same product: Asustor Data Master
CVE-2026-24936Same product: Asustor Data Master
CVE-2026-67245Same product: Asustor Data Master
CVE-2023-3698Same product: Asustor Data Master
CVE-2026-3179Same product: Asustor Data Master
CVE-2023-3697Same product: Asustor Data Master

Affected Assets

asustor
data master
4.1.0.rhu2 — 4.3.3.run1 · 5.0.0.ra82 — 5.1.4.rjv2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and static analysis can discover format-string vulnerabilities before deployment.

Input validation can reject or sanitize externally supplied format strings before they reach formatting functions.

Secure development standards and tools can mandate use of static format strings or safe formatting APIs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent external format strings via code review, static analysis, and safe APIs.

ID.RA-01 partial match
prevents

Vulnerability identification can discover existing format-string flaws but does not prevent their introduction.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect format-string vulnerabilities before release.

prevents

Secure SDLC mandates input validation and safe API usage that can prevent externally-controlled format strings.

prevents

Application security requirements can specify safe formatting functions and ban uncontrolled format strings.

prevents

Secure architecture principles discourage dangerous string-handling patterns that lead to format-string issues.

prevents

Secure coding standards directly forbid the use of untrusted format strings and prescribe safe alternatives.

References