Hard-coded CredentialsWeakness · CWE-798

CVE-2026-24444

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
SDMC NE6037 cable modem routers running firmware 7.1.6.0.25 and 7.1.6.1.9_B9 contain a hardcoded password vulnerability in the web management interface recovery endpoints (mgmt.php, npcmd.php) that allows unauthenticated attackers to gain root access by submitting the hardcoded credential to the recovery endpoint via HTTP. Attackers can leverage this hardcoded password to enable filtered SSH and Telnet services on the device, resulting in unauthenticated root-level remote access to the underlying system.

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

SDMC NE6037 cable modem routers running firmware versions 7.1.6.0.25 and 7.1.6.1.9_B9 contain a hardcoded password in the web management interface recovery endpoints (mgmt.php, npcmd.php). Unauthenticated attackers can submit this hardcoded credential via HTTP to gain root access and enable filtered SSH/Telnet services, resulting in unauthenticated root-level remote access to the device.

MitigationApply vendor firmware updates when available; meanwhile, block external access to the device's web management interface, SSH, and Telnet ports using network firewalls or disable remote management features entirely.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the router's web interface or check the device label/menu to confirm the model is SDMC NE6037
    Affected if The device is an SDMC NE6037 cable modem router
  2. Check the installed firmware version
    Log into the router web interface and navigate to the status or system information page to view the firmware version, or use the command line and run 'show version' or check /proc/version if accessible
    Affected if The firmware version is 7.1.6.0.25 or 7.1.6.1.9_B9
  3. Determine if the web management interface is exposed externally
    Review router firewall settings and port forwarding rules to check if the web interface (HTTP/HTTPS on ports 80/443) is accessible from external networks rather than only from the local LAN
    Affected if The web management interface (mgmt.php, npcmd.php endpoints) is reachable from untrusted networks
  4. Verify SSH or Telnet service status
    Check router settings for SSH or Telnet service enablement, or attempt to connect to the router's IP on ports 22 (SSH) or 23 (Telnet) from the network
    Affected if SSH or Telnet services are enabled and accessible on the device
  5. Confirm recovery endpoints are accessible
    Attempt to access the specific endpoints mgmt.php and npcmd.php via HTTP (for example, http://routerIP/mgmt.php) from an authorized position to verify they respond
    Affected if The recovery endpoints mgmt.php and npcmd.php are reachable and respond to requests

A user is affected if they have an SDMC NE6037 router running firmware version 7.1.6.0.25 or 7.1.6.1.9_B9 with the web management interface externally accessible, as this allows unauthenticated attackers to use the hardcoded credential on recovery endpoints for root access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware updates when available; meanwhile, block external access to the device's web management interface, SSH, and Telnet ports using network firewalls or disable remote management features entirely.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24444 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