CVE-2026-113735

D-Link DCS-6501LH aoni_ipc mydlink_set_root_pwd weak credentials

  • Medium 6.3
  • A public exploit reference is listed

Description

A vulnerability was determined in D-Link DCS-6501LH 3.03.02. Affected by this vulnerability is the function mydlink_set_root_pwd of the file /mnt/mtd/aoni_ipc. Executing a manipulation can lead to use of weak credentials. The attack may be launched remotely. The attack requires a high level of complexity. The exploitation appears to be difficult. The exploit has been publicly disclosed and may be utilized.

Key facts

Published
20 Oct 2026
Last changed
21 Oct 2026
Assigned by
VulDB
EPSS
0.691% likely to be exploited in the next 30 days, higher than 53.444% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: poc; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.3CVSS 4.0, Mediumfrom the CNA (VulDB)CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
  • 3.7CVSS 3.1, Lowfrom the CNA (VulDB)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R
  • 3.7CVSS 3.0, Lowfrom the CNA (VulDB)CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:X/RC:R
  • 2.6CVSS 2.0, Lowfrom the CNA (VulDB)AV:N/AC:H/Au:N/C:P/I:N/A:N/E:POC/RL:ND/RC:UR

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
D-LinkDCS-6501LH
  • 3.03.02 (affected)

Timeline

  1. 20 Oct 2026 Advisory disclosed
  2. 20 Oct 2026 VulDB entry created
  3. 20 Oct 2026 VulDB entry last update
  4. 20 Oct 2026 Published

Weakness

References