Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-5983: Buffer Overflow in D-Link DIR-605L formSetDDNS

Published Apr 9, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.4High · v4
EPSS0.70%54th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
D-Link
IdentifiersCVE-2026-5983CWE-120 · Buffer Copy without Checking Size…

CVE-2026-5983 is a remotely exploitable buffer overflow vulnerability in D-Link DIR-605L firmware version 2.13B01. The flaw is reported in the formSetDDNS function exposed via the /goform/formSetDDNS POST request handler. According to the available information, an attacker can trigger the issue by manipulating the curTime argument, causing an out-of-bounds write condition consistent with a classic buffer overflow. The affected product is end-of-life and no longer supported by the vendor. Public exploit disclosure has been reported.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow a remote attacker to corrupt process memory in the web management interface handling DDNS configuration requests. Based on the reported severity vectors, the likely impact includes compromise of confidentiality, integrity, and availability, potentially up to arbitrary code execution in the context of the vulnerable service, device instability or crash, and full compromise of the affected router.

Mitigation

If you can’t patch tonight, do this now.

Remove affected DIR-605L devices from service where possible. If immediate replacement is not feasible, restrict access to the management interface and any exposed /goform endpoints to trusted administrative networks only, disable remote administration, place the device behind upstream filtering or ACLs, and monitor for suspicious POST requests targeting /goform/formSetDDNS, especially malformed curTime parameters. Because public exploit disclosure exists and the device is unsupported, mitigation should be treated as temporary risk reduction rather than a complete solution.

Remediation

Patch, then assume compromise.

There is no indication of a vendor-supported fix for D-Link DIR-605L 2.13B01, and the product is explicitly described as no longer supported by the maintainer. The primary remediation is to retire and replace affected devices with supported hardware. If an updated firmware release from the vendor exists outside the provided content, it should be applied, but such a fix is not confirmed by the available information.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
D-LinkDir-605l Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2026-5983 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-5983 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-5983?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-5983.
Is there a patch for CVE-2026-5983?
There is no indication of a vendor-supported fix for D-Link DIR-605L 2.13B01, and the product is explicitly described as no longer supported by the maintainer. The primary remediation is to retire and replace affected devices with supported hardware.
What products are affected by CVE-2026-5983?
D-Link Dir-605l Firmware.
How severe is CVE-2026-5983?
CVE-2026-5983 has a CVSS v4 score of 7.4 (High) and an EPSS score of 0.70% (54th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.