dbcve.org
Dnr 202l FirmwareOperating system · Dlink

CVE-2026-4197

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to after 2026-02-05 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was found in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326, DNS-340L, DNS-343, DNS-345, DNS-726-4, DNS-1100-4, DNS-1200-05 and DNS-1550-04 up to 20260205. Affected is the function RSS_Get_Update_Status/RSS_Update/RSS_Channel_AutoDownlaod/RSS_Add/RSS_Channel_Item_Downlaod/RSS_History_Item_List/RSS_Item_List of the file /cgi-bin/download_mgr.cgi. The manipulation results in command injection. The attack may be performed from remote. The exploit has been made public and could be used.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A command injection vulnerability exists in D-Link DNS-320, DNS-325, DNS-327L, and related NAS/camera devices in the download_mgr.cgi file. Multiple RSS-related functions (RSS_Get_Update_Status, RSS_Update, RSS_Channel_AutoDownload, RSS_Add, RSS_Channel_Item_Download, RSS_History_Item_List, RSS_Item_List) fail to sanitize input properly, allowing remote attackers to execute arbitrary OS commands via crafted requests.

MitigationIf firmware updates are available from D-Link, apply them immediately. If devices are end-of-life, isolate them on restricted network segments, disable the RSS/download functionality if possible, or replace with supported hardware.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dnr 202l FirmwareOperating system
Affected:<= 2026-02-05
Dnr 326 FirmwareOperating system
Affected:<= 2026-02-05
Dns 1100 4 FirmwareOperating system
Affected:<= 2026-02-05
Dns 120 FirmwareOperating system
Affected:<= 2026-02-05
Dns 1200 05 FirmwareOperating system
Affected:<= 2026-02-05
Dns 1550 04 FirmwareOperating system
Affected:<= 2026-02-05
Dns 315l FirmwareOperating system
Affected:<= 2026-02-05
Dns 320 FirmwareOperating system
Affected:<= 2026-02-05

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your D-Link device model
    Check the device label, web interface header, or system information page to confirm the exact model number (e.g., DNS-320, DNS-325, DNS-327L, DNR-202L, DNR-326, DNS-1100-4, DNS-120, DNS-1200-05, DNS-1550-04, DNS-315L)
    Affected if The device model matches one of the affected models listed in the CVE
  2. Check the installed firmware version
    Access the device web interface (usually via HTTP/HTTPS on the LAN IP), navigate to System > Firmware Upgrade or System Information page, and note the firmware version and build date
    Affected if The firmware version or build date is on or before 2026-02-05 (compare your version to the affected ranges provided)
  3. Verify download_mgr.cgi is accessible
    From a system on the same network, attempt to access http://<device_ip>/download_mgr.cgi (or /cgi-bin/download_mgr.cgi) using a web browser or curl command
    Affected if The CGI script responds, indicating the web interface is enabled and accessible
  4. Confirm RSS/download functionality is enabled
    Log into the device web interface and check the RSS, Download Manager, or Network Media section under Application or Storage settings to see if RSS or download features are configured or active
    Affected if RSS-related features, channel subscriptions, or download manager functionality is present and enabled on the device

Your device is likely affected if it is one of the listed D-Link models, runs firmware dated 2026-02-05 or earlier, has the web interface with download_mgr.cgi accessible, and has RSS/download features enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2026-02-05
Interim mitigation

If firmware updates are available from D-Link, apply them immediately. If devices are end-of-life, isolate them on restricted network segments, disable the RSS/download functionality if possible, or replace with supported hardware.

Fix this in Dnr 202l Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4197 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4197 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data