CVE-2026-24936
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 · uneditedWhen a specific function is enabled while joining a AD Domain from ADM, an improper input parameters validation vulnerability in a specific CGI program allowing an unauthenticated remote attacker to write arbitrary data to any file on the system. By exploiting this vulnerability, attackers can overwrite critical system files, leading to a complete system compromise. Affected products and versions include: from ADM 4.1.0 through ADM 4.3.3.ROF1 as well as from ADM 5.0.0 through ADM 5.1.1.RCI1.
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 confidenceImproper input validation vulnerability in a CGI program when a specific AD Domain join function is enabled in ADM (Arcserve Domain Manager), allowing unauthenticated remote attackers to write arbitrary data to any file on the system by exploiting the lack of input sanitization.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.1.0.rhu2, <= 4.3.3.rof1>= 5.0.0.ra82, < 5.1.2.re51CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Asustor Data Master installationConfirm the system is running Asustor Data Master (ADM) by checking the product name or model information in the system interface or by running 'adm' or 'asustor' related system commands if availableAffected if The system is not Asustor Data Master (ADM)
-
Check ADM versionLocate the installed ADM version in the system settings or control panel, typically found under System Information, About, or similar menu. Compare your version against the affected ranges: 4.1.0.rhu2 through 4.3.3.rof1, or 5.0.0.ra82 through 5.1.2.re50Affected if The installed version falls within 4.1.0.rhu2 <= version <= 4.3.3.rof1 OR 5.0.0.ra82 <= version < 5.1.2.re51
-
Verify AD Domain join function statusAccess the ADM management interface and navigate to Network settings, Domain/LDAP settings, or Active Directory configuration sections. Locate the AD Domain join function and determine whether it is enabled or disabledAffected if The AD Domain join function is enabled in ADM settings
-
Confirm CGI program presenceCheck if the web-based CGI interface is accessible and active on the ADM system, typically accessible via HTTP/HTTPS on the NAS management portAffected if The ADM web interface and CGI programs are exposed and accessible
A system is affected if it runs Asustor Data Master within versions 4.1.0.rhu2-4.3.3.rof1 or 5.0.0.ra82-5.1.2.re50 AND has the AD Domain join function enabled in the configuration.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scoped5.1.2.re51
Disable the specific AD Domain join function in ADM until vendor patches are applied; prioritize patching given the critical CVSS 9.8 severity and unauthenticated remote attack vector.
ADM 5.1.2.re51 (or latest available 5.x release); ADM 4.x users should migrate to latest 5.x release for ongoing security support
- 1. Identify the current ADM version installed on the ASUSTOR NAS by accessing ADM Settings > System > Firmware Update
- 2. For ADM 5.x users (versions 5.0.0 through 5.1.1.RCI1): Upgrade to ADM version 5.1.2.re51 or later, which contains the security fix
- 3. For ADM 4.x users (versions 4.1.0 through 4.3.3.ROF1): Upgrade to the latest available ADM 4.x version as provided by ASUSTOR, or consider migrating to ADM 5.x for continued security updates
- 4. After upgrading, verify the version by checking ADM Settings > System > Information
- 5. Review AD Domain join settings in ADM to ensure proper configuration after the update
- 6. Test the AD Domain functionality to confirm the vulnerability has been remediated and normal operations are restored
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation10.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24936 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24936 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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