# CVE-2026-4182: D-Link DIR-816 goahead form2Wl5RepeaterStep2.cgi stack-based overflow

> Remote attackers can execute arbitrary code via stack-based buffer overflow in the goahead web server of unsupported D-Link DIR-816 routers.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-jmxw-gwqc-xrm5

## What is CVE-2026-4182?

CVE-2026-4182 is a critical memory corruption vulnerability in Dlink Dir-816 Firmware, published on 15 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in D-Link DIR-816 1.10CNB05. This impacts an unknown function of the file /goform/form2Wl5RepeaterStep2.cgi of the component goahead. This manipulation of the argument key1/key2/key3/key4/pskValue causes stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. This vulnerability only affects products that are no longer supported by the maintainer.

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

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

It affects 1 product.


Products: Dlink Dir-816 Firmware.

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

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

## Is CVE-2026-4182 being exploited?

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

## Other vulnerabilities in Dlink Dir-816 Firmware

- [CVE-2025-45931](https://insights.sbomify.com/CVE-2025-45931/): Command injection in n/a (critical 9.8)
- [CVE-2024-57684](https://insights.sbomify.com/CVE-2024-57684/): Missing authorization in n/a (critical 9.8)
- [CVE-2023-24331](https://insights.sbomify.com/CVE-2023-24331/): Command injection in n/a (critical 9.8)
- [CVE-2024-24321](https://insights.sbomify.com/CVE-2024-24321/): Command injection in n/a (critical 9.8)
- [CVE-2023-39637](https://insights.sbomify.com/CVE-2023-39637/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4182 is a critical memory corruption vulnerability in Dlink Dir-816 Firmware, published on 15 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-4182 exists.

Affected product: Dlink Dir-816 Firmware. 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-4182/ (Markdown: https://insights.sbomify.com/CVE-2026-4182/index.md)
```

## Sources

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

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