D-Link NAS and recorder products were found to contain multiple remote stack-based buffer overflow vulnerabilities affecting /cgi-bin/app_mgr.cgi, /cgi-bin/webdav_mgr.cgi, and /cgi-bin/account_mgr.cgi. The issues were assigned CVE-2026-5211, CVE-2026-5212, and CVE-2026-5213 and impact a broad set of devices, including DNS-120, DNS-320 series, DNS-340L, DNS-345, DNS-726-4, DNS-1100-4, DNS-1200-05, and DNS-1550-04.
The flaws are triggered by crafted input to specific parameters: f_dir in the UPnP_AV_Server_Path_Del function, f_file in the Webdav_Upload_File function, and read_list in the cgi_adduser_to_session function. Because the vulnerabilities can be exploited remotely and public exploit details have been disclosed, exposed devices face an elevated risk of compromise and potential attacker weaponization in real-world attacks.

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
1 event from the most recent confirmed update back to the earliest known activity.
Three stack-based buffer overflow vulnerabilities affecting multiple D-Link NAS and recorder products were publicly disclosed: CVE-2026-5211 in /cgi-bin/app_mgr.cgi, CVE-2026-5212 in /cgi-bin/webdav_mgr.cgi, and CVE-2026-5213 in /cgi-bin/account_mgr.cgi. The flaws are remotely exploitable and the disclosures note public exploit details or exploit availability, raising the risk to exposed devices.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.