# CVE-2026-124562: D-Link DIR-878 HNAP SetWanSettings buffer overflow


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-xq98-q783-w24j

## What is CVE-2026-124562?

CVE-2026-124562 is a high-severity vulnerability in D-Link DIR-878, published on 9 Nov 2026. 

### Official description

A vulnerability was identified in D-Link DIR-878 1.20B05. Affected is the function SetWanSettings of the component HNAP Handler. The manipulation of the argument ConfigDNS/Primary/ConfigDNS/Secondary leads to buffer overflow. The attack may be initiated remotely. The exploit is publicly available and might be used. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-124562 being exploited?

There is no known exploitation of CVE-2026-124562 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124562 is a high-severity vulnerability in D-Link DIR-878, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124562 in the wild and no public exploit code.

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

## Sources

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

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