On this page (7 sections)

A critical vulnerability, CVE-2026-125086, has been recorded for the D-Link M60 router running firmware 1.12.B01. According to the NVD entry, the emDaemon MQTT Broker component contains hard-coded credentials, the issue can be reached remotely, and an exploit has been disclosed publicly.

If you run an M60 at a home, a small office or a branch site, or you manage such devices for clients, this is worth a quick review. Details are thin at the moment: the record is the main source, and no vendor fix or advisory is cited in the research we have.

What was reported

The NVD description says a vulnerability was found in the D-Link M60 on firmware 1.12.B01. It points to the function system in the file /etc/emDaemon/mosquitto.conf, part of the emDaemon MQTT Broker, and states that manipulation leads to hard-coded credentials. It adds that the attack can be executed remotely and that the exploit has been disclosed to the public.

The record was published on 2026-11-10. Its references include a GitHub repository, several VulDB entries and the D-Link home page. We have not reviewed those pages' contents, so we do not describe what they contain. Only one independent publisher covers the story so far, so treat details as preliminary.

What hard-coded credentials mean here

MQTT is a lightweight publish and subscribe messaging protocol often used by devices to talk to each other. A broker is the central service that receives and distributes those messages. On a mesh router, a broker like this can carry coordination traffic between nodes.

In general, hard-coded credentials are usernames or passwords embedded in a device's firmware or configuration instead of being set by the owner. Because they are built in, owners typically cannot rotate them, and a secret that becomes public can be tried against any exposed device that uses it. That describes the weakness class (CWE-259 and CWE-798) in general terms; it is not a confirmed detail of this particular device.

What we cannot say from the research: which accounts are affected, whether the credentials are the same on every unit, whether they can be changed by the owner, what access they grant, whether the broker is reachable from the internet by default or only from the local network, and what an attacker could do afterwards. The record says the attack can be executed remotely, but it does not explain the network conditions required.

Who is realistically exposed

  • Owners of a D-Link M60 on firmware 1.12.B01, the only version named in the record. Other versions are not mentioned either way.
  • Devices where the MQTT broker is reachable from the internet, or from a network segment you do not fully trust (guest Wi-Fi, shared building networks, a compromised laptop).
  • Agencies and IT providers who installed M60 units for customers and may not track their firmware.

Websites hosted elsewhere are not directly affected. The practical risk is to the network the router protects: office devices, cameras, point-of-sale systems or admin workstations used to manage websites.

How to check your exposure

  1. Log in to the router's admin interface and note the model and the firmware version. Compare it with 1.12.B01.
  2. Check whether remote management or any port forwarding is enabled, and turn off anything you do not need.
  3. From outside your network (for example a mobile connection), see whether your public IP answers on the standard MQTT ports. These are 1883 for plain MQTT and 8883 for MQTT over TLS, which are widely documented defaults; the research does not say which port this broker uses.
  4. Review the router's connected-device list and admin account list for anything you do not recognize.
Check from a machine OUTSIDE your network whether common MQTT ports are open on your public IP…Shell
nc -zv YOUR_PUBLIC_IP 1883
nc -zv YOUR_PUBLIC_IP 8883

A refused or timed-out connection is the result you want. Only run this against your own address. An open port does not prove the device is vulnerable, and a closed port from outside does not rule out access from inside the local network.

What to do now

The research does not name a fixed firmware version, so the steps below focus on reducing exposure and watching for an update.

  1. Confirm whether any D-Link M60 units run firmware 1.12.B01.
  2. Check the D-Link support site and your device's admin page for a newer firmware or a security advisory, and install it once available after reading its notes.
  3. Disable remote administration and remove port forwards to the router that you do not strictly need.
  4. Make sure the router's own admin password is unique and strong, and change it if it was ever shared or left at a default.
  5. Keep untrusted devices on a guest network, away from servers, workstations and payment equipment.
  6. If you suspect the router was accessed, back up the configuration, then reset it to factory settings and set it up again with new passwords.
  7. Where the device is not essential or no fix appears, consider placing it behind another firewall or replacing it.
Caution. A factory reset or firmware change interrupts connectivity for everything behind the router. Do it outside business hours, and save the configuration first.

Detection and monitoring

Because the fix status is unknown, monitoring matters. Watch your router's logs, if it keeps any, for logins or connections you do not recognize, and check for unexpected configuration changes such as new admin users, altered DNS settings or new forwarding rules. Unexplained slowdowns or devices appearing on the network are also worth investigating.

If the router sits in front of a business site or store, keep an eye on the public side as well. Webforta Monitor can alert you to uptime, certificate and DNS changes, which can help you notice if network settings are tampered with, though it cannot see inside the router. For wider guidance, see what to do if a website is hacked and the small business website security guide.

What we still do not know

  • Whether D-Link has acknowledged the issue or released a patched firmware. The research cites no vendor advisory.
  • Whether the exploit has been used against real devices. The record says it has been disclosed and may be used; it does not confirm attacks, and the CVE is not marked in CISA KEV.
  • Whether other M60 firmware versions or other D-Link models are affected.
  • Which credentials are involved, whether they can be changed, and the exact impact once they are known.

We treat the CVSS 9.3 score and the critical rating as what the CVE record lists, and will update the picture when a vendor statement or independent analysis appears.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-125086: A vulnerability has been found in D-Link M60 1.12.B01.nvd.nist.gov ·
  • D-Link
  • router
  • hard-coded credentials
  • MQTT
  • CVE-2026-125086