PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-16332 D-Link CVE debrief

A vulnerability was detected in D-Link DNS-320 1.0.2, impacting an unknown function of the file /mydlink/multi_uploadify.php. The vulnerability allows for unrestricted upload by manipulating the Filedata[] argument, and the attack can be carried out remotely. The exploit is now public and may be used. This vulnerability affects D-Link DNS-320 devices, which are commonly used for network-attached storage. Defenders should assess the exposure of these devices and prioritize verification of their potential for exploitation.

Vendor
D-Link
Product
DNS-320
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-07-21
Original CVE updated
2026-10-24
Advisory published
2026-07-21
Advisory updated
2026-10-24

Who should care

Defenders responsible for D-Link DNS-320 devices should assess exposure and potential for exploitation. This includes operators, security teams, and vulnerability management teams who are responsible for ensuring the security of these devices. Defenders should prioritize verifying exposure of D-Link DNS-320 devices to this vulnerability and assess the potential for exploitation.

Why it matters

Defenders should prioritize verifying exposure of D-Link DNS-320 devices to this vulnerability and assess the potential for exploitation.

  • Verify exposure of D-Link DNS-320 devices to this vulnerability
  • Assess the potential for exploitation
  • Review and apply vendor remediation steps when available

Technical summary

The vulnerability allows for unrestricted upload by manipulating the Filedata[] argument in the /mydlink/multi_uploadify.php file of D-Link DNS-320 1.0.2, and the attack can be carried out remotely. This vulnerability affects D-Link DNS-320 devices, which are commonly used for network-attached storage. The technical impact of this vulnerability is that an attacker could potentially upload malicious files to the device, leading to further exploitation. Defenders should prioritize verifying exposure of D-Link DNS-320 devices to this vulnerability and assess the potential for exploitation.

Defensive priority

Defenders should prioritize verifying exposure of D-Link DNS-320 devices to this vulnerability and assess the potential for exploitation.

Recommended defensive actions

  • Verify exposure of D-Link DNS-320 devices to this vulnerability
  • Assess the potential for exploitation
  • Review and apply vendor remediation steps when available
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
  • Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the scope of affected versions and remediation steps require verification from official sources. The D-Link DNS-320 1.0.2 device is a network-attached storage system that may be vulnerable to this exploit. Defenders should verify the exposure of these devices and assess their potential for exploitation.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-16332 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-16332

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-16332 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-16332

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.