CVE-2025-55582: D-Link DCS-825L firmware v1.08.01 contains a vulnerability in the watchdog script `mydlink-watch-dog.sh`, whic
CVE-2025-55582 is a medium-severity flaw (CVSS 6.6) affecting dcs-825l firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
D-Link DCS-825L firmware v1.08.01 contains a vulnerability in the watchdog script `mydlink-watch-dog.sh`, which blindly respawns binaries such as `dcp` and `signalc` without verifying integrity, authenticity, or permissions. An attacker with local filesystem access (via physical access, firmware modification, or debug interfaces) can replace these binaries with malicious payloads. The script executes these binaries as root in an infinite loop, le
Why this priority
- Public exploit reference
No fix is published yet: follow the downgrade or mitigation steps.
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2025-55582?
dcs-825l firmware: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2025-55582 being exploited?
CVE-2025-55582 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2025-55582 affect?
CVE-2025-55582 affects dcs-825l firmware. Severity is medium (CVSS 6.6). D-Link DCS-825L firmware v1.08.01 contains a vulnerability in the watchdog script `mydlink-watch-dog.sh`, which blindly respawns binaries such as `dcp` and `signalc` without verifying integrity, authenticity, or permissions. An attacker wit
How urgent is CVE-2025-55582?
Priority 32/100. Public exploit reference
Software pages
Related CVEs
- CVE-2025-55581 HIGH 7.3 UPGRADE D-Link DCS-825L firmware version 1.08.01 and possibly prior versions contain an insecure implementation in the