CVE-2026-125086
D-Link M60 emDaemon MQTT Broker mosquitto.conf system hard-coded credentials
A vulnerability has been found in D-Link M60 1.12.B01. Impacted is the function system of the file /etc/emDaemon/mosquitto.conf of the component emDaemon MQTT Broker. Such manipulation leads to hard-coded credentials. The attack can be executed remotely. The exploit has been disclosed to the public and may be used.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| M60 D-Link |
1.12.B01 (affected) | CNA: VulDB |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 10.0 critical |
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P | CNA: VulDB |
| 3.1 / 10.0 critical |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:C | CNA: VulDB |
| 3.0 / 10.0 critical |
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H/E:P/RL:X/RC:C | CNA: VulDB |
| 2.0 / 10.0 critical |
AV:N/AC:L/Au:N/C:C/I:C/A:C/E:POC/RL:ND/RC:C | CNA: VulDB |
Exploit evidence
- https://github.com/XueDugu/dlink-m60-easymesh-mqtt-credential-evidence
exploit · CNA: VulDB
References
- https://vuldb.com/vuln/433197CNA: VulDB · vdb-entry, technical-description
- https://vuldb.com/vuln/433197/ctiCNA: VulDB · signature, permissions-required
- https://vuldb.com/cve/CVE-2026-125086CNA: VulDB · third-party-advisory
- https://vuldb.com/submit/1042370CNA: VulDB · third-party-advisory
- https://github.com/XueDugu/dlink-m60-easymesh-mqtt-credential-evidenceCNA: VulDB · exploit
- https://www.dlink.com/CNA: VulDB · product
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.