# CVE-2026-129354: D-Link DIR-600L HNAP cgibin hnap_main stack-based overflow

> Remote attackers can trigger a stack overflow in the HNAP handler of D-Link DIR-600L routers, potentially executing code or crashing the device.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 15 Nov 2026
- **Also known as:** GHSA-j69h-pwm6-99pr

## What is CVE-2026-129354?

CVE-2026-129354 is a critical memory corruption vulnerability in D-Link DIR-600L, published on 15 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw has been found in D-Link DIR-600L 2.17b02. Affected by this issue is the function hnap_main of the file htdocs/cgibin of the component HNAP Handler. Executing a manipulation can lead to stack-based buffer overflow. The attack can be executed remotely. The exploit has been published and may be used.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.

An affected version is exposed as installed. No special setting or call is needed.


Products: D-Link Dir-600l.

CPE match criteria (CPE 2.3):

- `cpe:2.3:h:d-link:dir-600l:*:*:*:*:*:*:*:*` from 2.17b02 up to 2.17b02

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

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

## Is CVE-2026-129354 being exploited?

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

Public exploit code:

- D-Link DIR-600L 2.17b02 cgibin hnap_main: pre-auth stack overflow via SOAPAction (whitelist = substring test; action = tail after last '/'). MD5-verified firmware re-hosted under qemu-mipsel; shipped binary crashes 0x45454545 with saved-RA control, bounds-shim side passes. (github_poc): https://github.com/googlesky/CVE-2026-129354

## Fix prompt for AI coding agents

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

What it is: CVE-2026-129354 is a critical memory corruption vulnerability in D-Link DIR-600L, published on 15 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-129354 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

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

## Sources

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

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