# CVE-2026-112146: D-Link E15/M32/R15/R32 MQTT Broker passwd hard-coded credentials

> Hard-coded credentials in the MQTT Broker allow remote attackers to bypass authentication and take over affected D-Link devices.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-wwwx-2xcj-h3pf

## What is CVE-2026-112146?

CVE-2026-112146 is a medium-severity vulnerability in D-Link E15, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in D-Link E15, M32, R15 and R32. This issue affects some unknown processing of the file /etc/emDaemon/passwd of the component MQTT Broker. The manipulation results in hard-coded credentials. It is possible to launch the attack remotely. The exploit is now public and may be used.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2026-112146?


## How do I fix CVE-2026-112146?

No fix has been published for CVE-2026-112146 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-112146 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112146 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-112146 and fix it if it is affected.

What it is: CVE-2026-112146 is a medium-severity vulnerability in D-Link E15, published on 19 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112146 exists.

Affected product: D-Link E15. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-112146/ (Markdown: https://insights.sbomify.com/CVE-2026-112146/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-112146
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-112146
- OSV: https://osv.dev/vulnerability/CVE-2026-112146

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-112146/
Summaries are generated and may contain mistakes; the official description above is the record.