Quick answers
- Is CVE-2026-5212 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-5212 being exploited in the wild.
- How severe is CVE-2026-5212?
- High severity, with a CVSS score of 8.8, published 31 March 2026.
- Which products and versions are affected?
- D-Link DNS-120 up to 20260205; D-Link DNR-202L up to 20260205; D-Link DNS-315L up to 20260205; D-Link DNS-320 up to 20260205; and 4 more.
- Is there a fix for CVE-2026-5212?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-5212 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-5212?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A stack-based buffer overflow vulnerability exists in the 'Webdav_Upload_File' function within the '/cgi-bin/webdav_mgr.cgi' binary of multiple D-Link NAS and NVR models. The vulnerability is triggered by providing an excessively long string to the 'f_file' (filename) argument during a file upload request. Because the application fails to validate the length of this input before copying it to a local stack variable, an attacker can overwrite the function's return address. This can be exploited remotely by an authenticated user to achieve arbitrary code execution or cause a persistent denial of service (system crash). Public exploit code (PoC) has been disclosed.
Affected products
- D-Link DNS-120 up to 20260205
- D-Link DNR-202L up to 20260205
- D-Link DNS-315L up to 20260205
- D-Link DNS-320 up to 20260205
- D-Link DNS-320L up to 20260205
- D-Link DNS-320LW up to 20260205
- D-Link DNS-321 up to 20260205
- D-Link,versions: DNR-322L
Timeline
- 2026-03-31: disclosed: Vulnerability published on NVD