# CVE-2026-113735: D-Link DCS-6501LH aoni_ipc mydlink_set_root_pwd weak credentials


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-fv9g-4r87-q3vg

## What is CVE-2026-113735?

CVE-2026-113735 is a medium-severity vulnerability in D-Link DCS-6501LH, published on 20 Oct 2026. 

### Official description

A vulnerability was determined in D-Link DCS-6501LH 3.03.02. Affected by this vulnerability is the function mydlink_set_root_pwd of the file /mnt/mtd/aoni_ipc. Executing a manipulation can lead to use of weak credentials. The attack may be launched remotely. The attack requires a high level of complexity. The exploitation appears to be difficult. The exploit has been publicly disclosed and may be utilized.

Weakness: CWE-1391 (Use of Weak Credentials)

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


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

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

## Is CVE-2026-113735 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113735 is a medium-severity vulnerability in D-Link DCS-6501LH, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113735 exists.

Affected product: D-Link DCS-6501LH. 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-113735/ (Markdown: https://insights.sbomify.com/CVE-2026-113735/index.md)
```

## Sources

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

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