CVE-2026-5212Public exploitNetwork attack vector

Authenticated code execution via unchecked upload filename

Published Mar 31, 2026 · Updated Mar 31, 2026

Stack-based overflow in D-Link DNS and DNR firmware through 20260205 allows remote authenticated users to execute arbitrary code. A crafted multipart f_file filename is copied into a stack-local buffer in Webdav_Upload_File without a length check, overwriting the return address. Authenticated access to webdav_mgr.cgi is required; the demonstrated payload persistently crashes services, while return-address control enables code execution.

CVSS severity8.8
High
EPSS probability0.74%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Stack-based overflow in D-Link DNS and DNR firmware through 20260205 allows remote authenticated users to execute arbitrary code. A crafted multipart f_file filename is copied into a stack-local buffer in Webdav_Upload_File without a length check, overwriting the return address. Authenticated access to webdav_mgr.cgi is required; the demonstrated payload persistently crashes services, while return-address control enables code execution.

The record

CVE
CVE-2026-5212
Published
Mar 31, 2026
Updated
Mar 31, 2026
Vendor
D-Link
Product
DNR-322L
Classifications
CWE-787, CWE-119, CWE-121, T1190
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Mar 31, 2026CVE publishedPublication date reported by the CVE source.
  2. Mar 31, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=20260205

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

D-Link · DNR-322Lversion=20260205
D-Link · DNS-1100-04version=20260205
D-Link · DNS-325version=20260205
D-Link · DNS-726-4version=20260205
D-Link · DNS-320Lversion=20260205
D-Link · DNR-202Lversion=20260205
D-Link · DNS-340Lversion=20260205
D-Link · DNS-321version=20260205
D-Link · DNS-1550-04version=20260205
D-Link · DNS-343version=20260205
D-Link · DNS-315Lversion=20260205
D-Link · DNS-323version=20260205
D-Link · DNS-345version=20260205
D-Link · DNR-326version=20260205
D-Link · DNS-327Lversion=20260205
D-Link · DNS-326version=20260205
D-Link · DNS-120version=20260205
D-Link · DNS-320version=20260205
D-Link · DNS-1200-05version=20260205
D-Link · DNS-320LWversion=20260205

Published CVSS scores

9.0VulDBAV:N/AC:L/Au:S/C:C/I:C/A:C
7.4VulDBCVSS: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
8.8VulDBCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-787Out-of-bounds Write
CWE-119Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-121Stack-based Buffer Overflow
T1190Exploit Public-Facing Application

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo