dbcve.org
Data MasterOperating system · Asustor

CVE-2026-24935

MEDIUM · 5.6 CVSS v3.1 Published 2026-02-03
Fix available
A fix is available. Upgrade to 5.1.2.re51 or later.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable No privileges 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
A third-party NAT traversal module fails to validate SSL/TLS certificates when connecting to the signaling server. While subsequent access to device services requires additional authentication, a Man-in-the-Middle (MitM) attacker can intercept or redirect the NAT tunnel establishment. This could allow an attacker to disrupt service availability or facilitate further targeted attacks by acting as a proxy between the user and the device services. 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 confidence

A third-party NAT traversal module used in Archer Device Manager (ADM) does not validate SSL/TLS certificates when establishing connections to signaling servers. This allows a Man-in-the-Middle attacker to intercept or redirect the NAT tunnel establishment, potentially disrupting service or acting as a proxy for further attacks against device services.

MitigationImplement proper SSL/TLS certificate validation in the NAT traversal module, typically through a vendor patch or configuration update to enforce certificate verification before tunnel establishment.

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
Data MasterOperating system
Affected:>= 4.1.0.rhu2, <= 4.3.3.rof1>= 5.0.0.ra82, < 5.1.2.re51

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

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. Identify installed Asustor Data Master version
    Access the ADM admin interface or check system information page to find the exact firmware/software version number
    Affected if The version falls within >= 4.1.0.rhu2 and <= 4.3.3.rof1, OR >= 5.0.0.ra82 and < 5.1.2.re51
  2. Verify NAT traversal module is configured
    Check ADM settings for NAT traversal, tunnel, or signaling server configuration options. Look for features related to remote access or device management connectivity
    Affected if NAT traversal module is enabled and configured to connect to external signaling servers
  3. Inspect SSL/TLS certificate validation settings
    Examine NAT traversal configuration files or UI settings for any option related to certificate verification, trust validation, or SSL/TLS enforcement
    Affected if Certificate validation is disabled, set to optional, or explicitly configured to skip verification for NAT tunnel connections
  4. Check signaling server connection settings
    Review the connection configuration for signaling servers in ADM, noting whether secure connections are enforced or if insecure fallback is allowed
    Affected if Connections to signaling servers do not require valid SSL/TLS certificates or allow unverified certificates

User is affected if Asustor Data Master version is within the affected ranges AND the NAT traversal module is enabled with SSL/TLS certificate validation disabled or not enforced.

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.

dbcve · scoped
Upgrade available Upgrade to 5.1.2.re51 or later
Fixed in 5.1.2.re51
Interim mitigation

Implement proper SSL/TLS certificate validation in the NAT traversal module, typically through a vendor patch or configuration update to enforce certificate verification before tunnel establishment.

Recommended fix Moderate confidence

ADM 5.1.2.re51 or later

  1. 1. Log in to the Asustor ADM web interface
  2. 2. Navigate to Settings > System > Update & Backup (or similar update section)
  3. 3. Check for available system updates
  4. 4. Update to ADM version 5.1.2.re51 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Data Master Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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