Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege credentials (default or brute-forced)
-
DeliverySend crafted multipart POST to /load_file.cgi
-
ExploitTrigger out-of-bounds write in Multipart Handler
-
ExecutionCorrupt memory structures
-
ImpactExecute arbitrary code on device
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires low-privilege authentication on the D-Link DSM-G600 (PR:L per the CVSS 4.0 vector), meaning the attacker must hold valid credentials - this could be factory-default credentials, a guest account, or any user account on the device. The device's web interface must be reachable over the network (AV:N). No specific non-default configuration is required; the /load_file.cgi endpoint and its Multipart Handler appear to be standard components of firmware 1.01. Limiting exploitation: the PR:L requirement means unauthenticated network exploitation is not indicated by the available data; attackers must first obtain credentials. The device is legacy hardware with a limited installed base, which naturally constrains opportunistic targeting. |
| Impact | The CVSS 4.0 score of 7.4 reflects a network-exploitable flaw with high confidentiality, integrity, and availability impact but requires low-level authentication (PR:L), which moderates the raw score. No EPSS data was supplied, and the vulnerability is not listed in CISA KEV, indicating no confirmed widespread active exploitation at time of analysis. However, the public availability of exploit code (E:P confirmed in CVSS 4.0 supplemental metrics and by VulDB reporting) meaningfully elevates real-world risk beyond what the score alone implies. The DSM-G600 is legacy D-Link NAS hardware with no active vendor support, making patching effectively impossible through official channels; defenders managing any surviving units - even in small-office or home environments - should treat decommissioning or network isolation as the primary response. The absence of KEV listing should not be read as safety: PoC availability on unpatched embedded devices with weak authentication postures historically converts to exploitation quickly. |
| Exploit ScenarioDerived | An attacker with low-privilege credentials on the D-Link DSM-G600 (e.g., a guest account or default credentials left unchanged) sends a crafted HTTP multipart/form-data POST request to /load_file.cgi containing a malformed Content-Disposition or oversized boundary segment. The Multipart Handler writes beyond an allocated buffer, corrupting adjacent memory structures and enabling the attacker to redirect execution to attacker-controlled code. A public PoC demonstrating this technique is available in the referenced GitHub repository (https://github.com/dxz0069/WAVLINK-WN530H4-Command-Injection-in-set_add_routing/blob/main/DLINK-BOF-001-vulndb.md). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Aug 31, 2026
Out-of-bounds write in D-Link DSM-G600 firmware 1.01 exposes the device to remote memory corruption via a malformed multipart request to the /load_file.cgi endpoint. A low-privileged, network-adjacent or internet-accessible attacker can trigger CWE-787 in the Multipart Handler, potentially achieving arbitrary code execution with full confidentiality, integrity, and availability impact on the device. A public proof-of-concept exploit has been disclosed; no vendor patch has been identified, consistent with D-Link's typical end-of-life posture for legacy NAS hardware.
Earlier versions of this analysis (1)
Out-of-bounds write in the Multipart Handler of D-Link DSM-G600 firmware 1.01 allows remote low-privileged attackers to corrupt memory via a crafted multipart request to /load_file.cgi, with potential for arbitrary code execution on the device. The CVSS 4.0 score of 8.7 reflects high impact across confidentiality, integrity, and availability with low attack complexity and no user interaction required. A public proof-of-concept exploit is available, materially increasing near-term exploitation risk for any network-accessible deployment of this legacy NAS device.
RemediationAI
No vendor-released patch has been identified at time of analysis; the DSM-G600 is legacy hardware and D-Link does not reliably provide security updates for end-of-life NAS products. The primary recommended action is to decommission the device and replace it with a supported product. If decommissioning is not immediately possible, place the device behind a firewall with all inbound access to the web management interface (typically TCP 80/443 and 8080) blocked from untrusted networks, including the internet - this neutralizes the AV:N attack vector. Disable remote access features if the device firmware permits. Restricting authenticated access to the /load_file.cgi endpoint specifically, if the device supports ACL configuration, reduces but does not eliminate risk since internal network exploitation remains possible. No official advisory URL with a patch version was found in the provided references.
Affected VersionsENISA
Affected Packages
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 /load_file.cgi, a CGI endpoint on the D-Link DSM-G600 NAS device (firmware 1.01, CPE: cpe:2.3:a:d-link:dsm-g600:*:*:*:*:*:*:*:*). The Multipart Handler within this CGI script performs insufficient boundary or length validation when processing multipart form-data submissions, resulting in a heap or stack write beyond an allocated buffer (CWE-787: Out-of-Bounds Write). On embedded Linux-based NAS devices of this era, such overflows in CGI handlers frequently permit overwriting function pointers or return addresses, enabling code execution under the web server process context. The CVSS 4.0 vector (E:P) confirms a PoC is publicly available.
Know when Dsm G600 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Network-accessible CGI endpoint, no complexity; PR:L confirmed by CVSS 4.0 vector; no scope change as impact is contained to the NAS device.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
3DescriptionCVE.org
A weakness has been identified in D-Link DSM-G600 1.01. This affects an unknown function of the file /load_file.cgi of the component Multipart Handler. Executing a manipulation can lead to out-of-bounds write. The attack may be launched remotely. The exploit has been made available to the public and could be used for attacks.
Articles & Coverage 2
Technical POC Analysis
The confirmed defect is an out-of-bounds write / buffer overflow in the multipart handler of /loadfile.cgi, served by estorage/bin/http in DSM-G600 REVA 1.01 firmware (ARM big-endian, binary SHA1 b12…
Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.
Latest POC
1 PoC candidate from github (unverified)
Sign in to open the public PoC links collected for this CVE.
Executive ViewAI
D-Link DSM-G600 NAS firmware 1.01 contains an out-of-bounds write vulnerability allowing remote attackers to execute arbitrary code on affected devices via a malformed request to the /load_file.cgi endpoint. Public exploit code is available and no vendor patch is forthcoming from D-Link. Organizations using this legacy hardware face immediate risk to stored data and device integrity, with potential for lateral movement if the device is network-connected to critical systems.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) restrict network access to affected devices through segmentation, limiting exposure to internal-only or trusted subnets; (2) disable web management interface if operationally feasible; (3) deploy intrusion detection/prevention signatures to block malformed multipart requests; (4) implement logging and monitoring to detect unauthorized access or suspicious process execution on affected devices. These controls reduce exploitation likelihood but do not eliminate the vulnerability; hardware replacement or air-gapped isolation is the definitive remediation.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
EUVD-2026-68461
GHSA-mpcx-h3r3-22wg
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB