Skip to main content

D-Link DIR-600L CVE-2026-129354

| EUVDEUVD-2026-125951 CRITICAL
Stack-based Buffer Overflow (CWE-121)
2026-11-15 VulDB GHSA-j69h-pwm6-99pr
9.3
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach device HNAP interface over network
  2. Delivery
    Send crafted HNAP SOAPAction request
  3. Exploit
    Overflow stack buffer in hnap_main (cgibin)
  4. Execution
    Hijack control flow / execute code
  5. Impact
    Full device compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires network reachability to the device's HNAP Handler endpoint (the cgibin hnap_main function), reached via the web/management interface; the realistic worst case is a DIR-600L with the HNAP/HTTP interface exposed to the WAN, while LAN-only exposure limits attackers to the local network segment. Per the CVSS vector (PR:N/UI:N) no authentication or user interaction is needed. The precise trigger (which SOAPAction field or parameter overflows the buffer) is referenced by the public advisory title (HNAP SOAPAction) but the exact overflowing input is not detailed in the available sources. The main limiting factor is deployment scope: DIR-600L is an end-of-life model with a shrinking install base, and exploitation impact is confined to affected D-Link DIR-600L 2.17b02 firmware.

Impact

The input CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N with all vulnerable-system and subsequent-system impacts High) describes a remotely reachable, unauthenticated, low-complexity stack-based buffer overflow in the HNAP handler, which is consistent with the description ('attack can be executed remotely'). The vuln.today decision label is act_now, which signals high urgency. However, these signals should be weighed against mitigating real-world factors: exploitation status is only a published PoC reference (Exploitation Flag E:P / 'Proof-of-Concept'), NOT confirmed active exploitation - this CVE is not listed in CISA KEV and no EPSS probability was provided in the input, so widespread opportunistic exploitation cannot be asserted. The D-Link DIR-600L is an end-of-life consumer/SOHO router with a small, declining deployment footprint, so despite the 9.3 score the aggregate real-world risk is bounded by product prevalence and exposure (routers with WAN-side HNAP exposed are the primary at-risk population). Net: a genuinely severe, trivially exploitable flaw on affected devices, but the act_now label reflects severity and ease of exploitation rather than evidence of mass in-the-wild campaigns; prioritize for any surviving DIR-600L deployments, especially WAN-exposed ones.

Exploit ScenarioDerived

An attacker with network reach to the device (notably if the HNAP/web management interface is exposed to the WAN) sends a crafted HNAP SOAP request with an oversized SOAPAction or parameter value to the cgibin hnap_main function, overflowing a stack buffer. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no authentication or user interaction is required, enabling remote code execution or device takeover. A public PoC reference exists (GitHub advisory), but it is not verified as working exploit code, so reliability of a weaponized exploit is unconfirmed.

Act Now Prioritize within 24-48h. Why: CRITICAL severity + public POC available.
No patch listed yet

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Nov 15, 2026

Remote, unauthenticated stack-based buffer overflow in the HNAP handler (cgibin hnap_main) of D-Link DIR-600L firmware 2.17b02. A network-reachable attacker who can send crafted HNAP/SOAP requests to the device's web management interface can overwrite stack memory, potentially achieving code execution with the privileges of the HTTP service; the CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N, all impacts High) matches this worst case, and the realistic exposure scenario is a router with the HNAP/HTTP interface reachable from the WAN, while LAN-only deployments confine attackers to the local segment. A public advisory with exploit reference material has been published (a GitHub router-firmware advisory), and vuln.today prioritizes the issue as act_now, though the PoC is a reference not verified as working exploit code and no CISA KEV entry is reported.

Earlier versions of this analysis (1)
v1 Nov 15, 2026 - 01:10 CVSS 10.0

Remote stack-based buffer overflow in the HNAP handler of D-Link DIR-600L firmware 2.17b02 (hnap_main in htdocs/cgibin) allows an unauthenticated network attacker to corrupt memory via a manipulated HNAP request, with potential for code execution at the highest severity (CVSS 4.0 base 10.0; independently assessed CVSS 3.1 9.8). The CVSS vector (AV:N/AC:L/AT:N/PR:N/UI:N) states no authentication, no user interaction and no special configuration are required once the HNAP management interface is reachable, so practical risk is concentrated on units whose management plane is exposed beyond the local segment. A public PoC reference exists in a GitHub router-firmware advisory; it is not verified as working exploit code, and no CISA KEV entry is present in the supplied data, though the source is tracked with an act_now decision label given the pre-auth, network-reachable nature of the flaw.

RemediationAI

No vendor-released fixed firmware version is identified in the available sources for DIR-600L 2.17b02, so the primary action is to treat the device as unsupported and replace it with a router still receiving security updates; confirm the current support status through D-Link at https://www.dlink.com/ and monitor the VulDB entry https://vuldb.com/vuln/437417 for updates. As compensating controls, disable remote/WAN management so the HNAP and web administration interfaces are reachable only from the LAN, which removes the remote attack path at the cost of losing remote administration; restrict the management interface to trusted administrative hosts via firewall rules or network segmentation, understanding that any host on the permitted segment can still reach the vulnerable handler; and block inbound access to the device's HTTP management port at the network perimeter. These measures reduce exposure but do not fix the underlying stack overflow, and none of the sources indicate a patch or a vendor workaround beyond limiting reachability.

Affected VersionsENISA

DIR-600L 2.17b02

Affected Packages

euvd dir_600l no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The affected component is the HNAP (Home Network Administration Protocol) handler implemented in the device's cgibin CGI binary, function hnap_main, in DIR-600L firmware 2.17b02; CPE cpe:2.3:a:d-link:dir-600l:*:*:*:*:*:*:*:* covers the model. HNAP is a SOAP-over-HTTP management protocol used by D-Link and other consumer routers to expose configuration and status operations to clients and management tools, and the public advisory title points at the SOAPAction header as the relevant input surface. The flaw is classified as CWE-121, stack-based buffer overflow, meaning a length-unvalidated copy of attacker-supplied request data into a fixed-size stack buffer; the exact overflowing field or parameter is not detailed in the available sources, so the trigger should be treated as unconfirmed beyond the SOAPAction reference. Because the requests are parsed by the HTTP-side management service, exploitability depends on whether the HNAP endpoint is reachable - WAN-exposed management gives remote attackers the CVSS-vector-aligned path, whereas LAN-only configurations restrict abuse to hosts on the local segment. DIR-600L is an end-of-life consumer router, limiting both the install base and the vendor's likely remediation path.

Know when Dir 600L gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 9.3 CRITICAL
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
vuln.today AI 9.8 CRITICAL

Remote, low-complexity, unauthenticated stack overflow in the HNAP cgibin handler yields AV:N/AC:L/PR:N/UI:N with full code-execution impact on the device (C/I/A:H).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
High

Lifecycle Timeline

3
Analysis Updated
Nov 15, 2026 - 01:42 vuln.today
v2 - CVSS changed
CVSS changed
Nov 15, 2026 - 01:37 NVD
10.0 (CRITICAL) 9.3 (CRITICAL)
CVE Published
Nov 15, 2026 - 00:45 cve.org
CRITICAL 10.0

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

D-Link DIR-600L routers running firmware 2.17b02 contain a critical, unauthenticated remote stack buffer overflow in the HNAP handler that can lead to full device compromise. Any organization with these routers exposed to the internet faces immediate risk of unauthorized code execution, potentially allowing attackers to intercept or manipulate network traffic. Leadership should prioritize identification and remediation of these devices, as exploitation could disrupt business operations and expose sensitive data.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict WAN access to HNAP/HTTP interfaces via firewall rules, place devices behind VPN or isolated VLANs, monitor for anomalous HNAP/SOAP requests, and plan device replacement.

Threat Intelligence Overview

Prevalence
Low
end-of-life D-Link consumer SOHO router, small declining install base
Exploit
POC
Public exploit code exists
Social Media
6
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC Yes
EPSS N/A
Patch available No
Active threat No
Deciding rule
CRITICAL severity + public POC available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Out-of-Cycle
Exploitation· derived
Poc
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Very High

Priority Score

66
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy