CVE-2026-4182
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStack-based buffer overflow in D-Link DIR-816 1.10CNB05 router's goahead web server component. The form2Wl5RepeaterStep2.cgi handler fails to properly bounds-check the key1/key2/key3/key4/pskValue parameters before copying them to stack buffers, allowing remote attackers to potentially execute arbitrary code with the privileges of the web server.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.10cnb05CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelAccess the router's web admin interface or check the device label/metadata to confirm the model is D-Link DIR-816Affected if The device is not a D-Link DIR-816 model
-
Confirm firmware versionLog into the router's web interface and navigate to Status or System settings to view the firmware version, or use the router's upgrade page to check the current versionAffected if Firmware version is 1.10CNB05
-
Verify web server is enabledAttempt to access the router's web management interface by entering the router's IP address in a browser (typically 192.168.0.1 or 192.168.1.1)Affected if The web interface responds and is accessible
-
Check network exposure of management interfaceDetermine if the router's web interface is accessible from external networks by testing remote IP access or reviewing firewall rulesAffected if The management web interface is exposed to untrusted networks (not behind a firewall or VPN)
-
Verify vulnerable CGI handler existsCheck if the form2Wl5RepeaterStep2.cgi endpoint exists by attempting to access it via HTTP POST to the router's web interface path /form2Wl5RepeaterStep2.cgiAffected if The CGI handler responds (even with an error) indicating the vulnerable component is present
The environment is affected if it is a D-Link DIR-816 router running firmware version 1.10CNB05 with its web management interface accessible (especially from untrusted networks), as the vulnerable form2Wl5RepeaterStep2.cgi handler will be present and exploitable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedReplace the end-of-life D-Link DIR-816 device, as no vendor patch is available. If immediate replacement is not feasible, implement network segmentation to restrict access to the router's web management interface from untrusted networks.
- This vulnerability affects D-Link DIR-816 firmware 1.10CNB05, which D-Link has explicitly stated is no longer supported.
- Replace the affected D-Link DIR-816 router with a currently supported model from D-Link or another vendor.
- If immediate replacement is not possible, disable the router's web management interface from the internet by ensuring remote administration is turned off in the device settings.
- Place the affected device behind a properly configured firewall with no exposed web management ports to the internet.
- Monitor the network for any suspicious traffic targeting the /goform/form2Wl5RepeaterStep2.cgi endpoint.
- Consider deploying an intrusion detection/prevention system (IDS/IPS) to detect and block exploitation attempts targeting this buffer overflow vulnerability.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4182 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data