Skip to main content
Vulnerability Database/CVE-2026-112146

CVE-2026-112146: D-Link Router Authentication Bypass Vulnerability

CVE-2026-112146 is an authentication bypass vulnerability in D-Link E15, M32, R15, and R32 routers caused by hard-coded credentials in the MQTT Broker component. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-112146 Overview

CVE-2026-112146 is a hard-coded credentials vulnerability affecting multiple D-Link EAGLE PRO AI mesh devices. The flaw resides in the /etc/emDaemon/passwd file used by the device's MQTT Broker component. Static credentials embedded in this file allow authenticated network attackers to interact with the broker across any affected deployment. The weakness is classified under [CWE-259: Use of Hard-coded Password]. Public proof-of-concept material is available on GitHub, increasing the likelihood of opportunistic exploitation against exposed devices.

Critical Impact

Attackers with network reach to the MQTT Broker can reuse the embedded credentials to read or publish messages, impacting confidentiality, integrity, and availability of mesh communications.

Affected Products

  • D-Link E15
  • D-Link M32
  • D-Link R15
  • D-Link R32

Discovery Timeline

  • 2026-10-19 - CVE CVE-2026-112146 published to the National Vulnerability Database
  • 2026-10-19 - Last updated in NVD database

Technical Details for CVE-2026-112146

Vulnerability Analysis

The affected D-Link devices ship with a fixed credential set stored in /etc/emDaemon/passwd. This file supplies authentication material to the local MQTT Broker that supports EasyMesh coordination between EAGLE PRO AI nodes. Because the credentials are identical across firmware images, any attacker who recovers them from one device can authenticate against every device of the same model.

MQTT (Message Queuing Telemetry Transport) brokers typically mediate configuration, telemetry, and mesh control messages. Reusable broker credentials let an attacker subscribe to topics containing device state and publish crafted messages that influence routing or mesh behavior. The vulnerability is tracked under [CWE-259] and is reachable over the network with only low privileges required.

Root Cause

The root cause is static credential provisioning. The vendor embedded a shared password in /etc/emDaemon/passwd rather than generating a unique secret per device at first boot. Firmware extraction or filesystem access on one unit discloses the credential for the entire product line.

Attack Vector

Exploitation requires network access to the MQTT Broker port exposed by the device. An attacker authenticates with the recovered credentials and then interacts with broker topics. No user interaction is needed. Public proof-of-concept evidence is published at the GitHub PoC Repository and the accompanying PoC Code directory.

No verified exploitation code is reproduced here. Refer to the published PoC and the VulDB entry for CVE-2026-112146 for technical artifacts.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-112146

Indicators of Compromise

  • Unexpected MQTT CONNECT packets to the device's broker port from untrusted source addresses.
  • MQTT SUBSCRIBE or PUBLISH activity on EasyMesh control topics originating outside the mesh.
  • Authentication events in device logs showing the hard-coded account in use from unusual client identifiers.

Detection Strategies

  • Inspect network traffic for MQTT sessions on affected D-Link devices and correlate client IDs against known mesh members.
  • Review firmware images for the presence of /etc/emDaemon/passwd and flag deployments running vulnerable builds.
  • Alert on any MQTT broker reachability from WAN interfaces or non-management network segments.

Monitoring Recommendations

  • Capture broker traffic at the network edge and baseline normal publish and subscribe patterns per device.
  • Enable syslog export from the devices and forward MQTT authentication events to a central log platform.
  • Monitor for new or anomalous MQTT topic subscriptions that could indicate reconnaissance of mesh state.

How to Mitigate CVE-2026-112146

Immediate Actions Required

  • Restrict the MQTT Broker to the device's internal mesh interface and block external access with firewall rules.
  • Place affected devices on a segmented management VLAN that is not routable from client or guest networks.
  • Audit D-Link EAGLE PRO AI deployments for exposed broker ports and remove them from the public internet.

Patch Information

No vendor patch is referenced in the current advisory data. Monitor the D-Link Official Website and the VulDB vulnerability record #422251 for firmware updates addressing the hard-coded credential in /etc/emDaemon/passwd.

Workarounds

  • Block inbound traffic to the MQTT Broker port on the WAN and non-mesh interfaces of E15, M32, R15, and R32 devices.
  • Disable the EasyMesh feature where mesh functionality is not required, which removes the broker's operational need.
  • Deploy network access control to limit which hosts can reach the device management plane.
bash
# Configuration example: restrict MQTT broker exposure using iptables
iptables -A INPUT -i wan0 -p tcp --dport 1883 -j DROP
iptables -A INPUT -i wan0 -p tcp --dport 8883 -j DROP

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.