dbcve.org
Dir 816 FirmwareOperating system · Dlink

CVE-2026-4184

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability was detected in D-Link DIR-816 1.10CNB05. Affected by this vulnerability is an unknown functionality of the file /goform/form2Wl5BasicSetup.cgi of the component goahead. Performing a manipulation of the argument pskValue results in stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit is now public and may be used. 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 confidence

Stack-based buffer overflow in D-Link DIR-816 1.10CNB05 router's goahead web server component. The vulnerability exists in the /goform/form2Wl5BasicSetup.cgi handler when processing the pskValue parameter (wireless PSK), allowing remote attackers to overflow the stack and potentially execute arbitrary code.

MitigationSince the affected product is end-of-life and no longer supported by D-Link, there is no vendor patch. Mitigation requires either replacing the device with a supported model or implementing strict network access controls to prevent unauthorized access to the router's management interface.

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
Dir 816 FirmwareOperating system
Affected:= 1.10cnb05

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is D-Link DIR-816
    Access the router's web interface or check the device label/menu for the exact model number. The vulnerability applies only to the DIR-816 hardware model.
    Affected if The device is not a D-Link DIR-816 router.
  2. Check firmware version is 1.10CNB05
    Log into the router web interface and navigate to the System/Status page to view the firmware version, or use SNMP or the router's API if available to query the version information.
    Affected if The installed firmware version is 1.10CNB05 exactly.
  3. Verify the goahead web server is running and accessible
    Check if the router's HTTP/HTTPS management interface is listening on ports 80 or 443 by scanning the router's IP address or checking local network configuration.
    Affected if The goahead web server is enabled and accessible on the network.
  4. Confirm wireless configuration interface is accessible
    Attempt to access the wireless settings page or the /goform/form2Wl5BasicSetup.cgi endpoint (requires authentication). Check if the form2Wl5BasicSetup.cgi handler exists on the device.
    Affected if The wireless basic setup form handler is present and reachable.

You are affected if you have a D-Link DIR-816 router running firmware version 1.10CNB05 with the web interface accessible, as the stack buffer overflow can be triggered via the pskValue parameter in the /goform/form2Wl5BasicSetup.cgi handler.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the affected product is end-of-life and no longer supported by D-Link, there is no vendor patch. Mitigation requires either replacing the device with a supported model or implementing strict network access controls to prevent unauthorized access to the router's management interface.

Recommended fix High confidence
  1. Replace the D-Link DIR-816 router with a currently supported model from D-Link or another vendor, as this device is no longer supported by the manufacturer.
  2. If replacement is not immediately possible, isolate the device on a restricted network segment with firewall rules limiting access to the web management interface.
  3. Disable remote web management (HTTP/HTTPS) on the router if not absolutely necessary, restricting access to local network only.
  4. Monitor the network for any suspicious activity targeting the affected device.
Caveat The DIR-816 1.10CNB05 firmware is end-of-life and no longer supported by D-Link; there is no available upgrade path to a fixed version.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dir 816 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $880
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4184 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4184 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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