Skip to content
IoT

CVE-2026-85224

8.5
High
EPSS 2%Sep 4, 2026

Remote OS command injection in D-Link DNS-320 via file_sharing.cgi 'fileurl' parameter.

common questions

Is CVE-2026-85224 being exploited?

Not confirmed. CVE-2026-85224 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.2% probability of exploitation in the next 30 days.

How severe is CVE-2026-85224?

CVE-2026-85224 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-85224?

Not known from our data. No patch reference has been recorded for CVE-2026-85224, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-85224 affect?

CVE-2026-85224 affects D-Link DNS-320 ShareCenter firmware 2.06B01, DNS-320 NAS appliances (file_sharing.cgi). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-85224?

Isolate affected devices, disable remote/port-forwarding to NAS, block CGI access, monitor logs, apply vendor patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
D-Link DNS-320 ShareCenter firmware 2.06B01DNS-320 NAS appliances (file_sharing.cgi)
impact

Remote OS command injection via fileurl allows arbitrary command execution and full device compromise, data exposure, or pivoting.

action required

Immediate action required

affected versions
D-Link DNS-320 ShareCenter
  • affected2.06B01

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free