# CVE-2026-113736: D-Link DHP-W610AV HNAP Login defaultvalue.xml login_prepare_hnap empty password


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-7g5v-6vjx-9m7w

## What is CVE-2026-113736?

CVE-2026-113736 is a critical vulnerability in D-Link DHP-W610AV, published on 21 Oct 2026. 

### Official description

A vulnerability has been found in D-Link DHP-W610AV 1.02EUb03. The impacted element is the function login_prepare_hnap of the file etc/defnodes/defaultvalue.xml of the component HNAP Login. The manipulation of the argument Password leads to empty password in configuration file. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

Weakness: CWE-259 (Use of Hard-coded Password), CWE-258 (Empty Password in Configuration File)

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


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

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

## Is CVE-2026-113736 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113736 is a critical vulnerability in D-Link DHP-W610AV, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113736 exists.

Affected product: D-Link DHP-W610AV. 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-113736/ (Markdown: https://insights.sbomify.com/CVE-2026-113736/index.md)
```

## Sources

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

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