Check these three things.
-
System owner: confirm each Synology NAS runs DSM 7.2.2-72806-1 or another fixed DSM or BeeStation OS build.
Affected versions and fixes
- DiskStation Manager (DSM), from Synology's advisory and the CVE record:
- 7.2.2 before 7.2.2-72806-1.
- 7.2.1 before 7.2.1-69057-6.
- 7.2 before 7.2-64570-4.
- 7.1 before 7.1.1-42962-7.
- BeeStation OS (BSM) 1.0 and 1.1 before 1.1-65374.
- Compare the full installed version, including the build and update suffix, with the listed fix for that release. A device on 7.2.2 is fixed only at 7.2.2-72806-1 or later.
- Synology's DSM advisory lists no mitigation other than the update.
- Record for each device:
- Model, installed version and build.
- Source of that record.
- Date checked.
- DiskStation Manager (DSM), from Synology's advisory and the CVE record:
-
Network owner: check whether each NAS sign-in page can be reached from the Internet.
When the risk applies
- No login or user action is needed (CVSS 3.1 AV:N/PR:N/UI:N).
- Rapid7 researcher Ryan Emmons (@the_emmons on X), credited by Synology, showed the flaw is reached through the DSM web sign-in on port 80, 443, 5000, 5001, 6600 or 6601, depending on the device.
- Rapid7 found every DiskStation it tested vulnerable in the default configuration, and BeeStation vulnerable in its non-default Local Access setting.
- Check router port forwarding, firewall rules and any service that publishes the NAS sign-in page.
- AV:N also covers internal networks. A device not on the Internet can still be reached from inside.
-
Security owner: check each NAS for unknown accounts, scheduled tasks, packages and file changes.
What the records can show
- CISA's KEV entry asks for forensic triage on affected devices.
- Rapid7's demonstration on DSM ran code as root.
- Records to review:
- Unexpected scheduled tasks.
- Unknown user accounts or packages.
- Unexpected outbound connections.
- Changed, deleted or encrypted files.
- Limits:
- Clean records do not prove no attack happened.
- Missing records leave the question open.
- An existing compromise can persist after an update. Complete the compromise check even after patching.
If records show a break-in, start incident response now. Update every affected NAS today. CISA gave US federal agencies until November 21, 2026.
Do Now
- System owner: update DSM to 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4 or 7.1.1-42962-7, and BeeStation OS to 1.1-65374.
Proof the update is done
- Completion evidence for each device:
- Version and build installed after the update.
- Source of that record.
- Date checked.
- Completion evidence for each device:
- Network owner: remove Internet access to each NAS sign-in page that does not need it.
What to know
- CISA asks owners to evaluate each device's Internet exposure.
- Use a private connection such as a VPN for remote administration.
- This lowers exposure. It is not the fix.
Do Next
- Security owner: complete a compromise check on every NAS that ran an affected build with its sign-in page reachable.
What to check
- Use the records listed in the third check.
- Start with devices reachable from the Internet.
- Record what was checked and the date.
Check your own records.
- Use your approved AI tool.
- Require evidence. Flag unknowns.
Read the prompt
The reported finding
Synology system plugin daemon code execution (CVE-2024-10441)
Original advisory →- Required conditions
- DSM 7.2.2 before 7.2.2-72806-1, 7.2.1 before 7.2.1-69057-6, 7.2 before 7.2-64570-4, 7.1 before 7.1.1-42962-7, or BeeStation OS 1.0 or 1.1 before 1.1-65374, with network access to the device.
- Reported outcome
- Synology: improper encoding or escaping of output in the system plugin daemon lets remote attackers run code; CVSS 3.1 9.8 Critical; weakness CWE-116. Rapid7: code runs as root, with no login, through the web sign-in flow; Rapid7 classifies the weakness as CWE-141.
Fix guidance
- Synology (@Synology on X) advisory Synology-SA-24:20, first published November 5, 2024: fixed in DSM 7.2.2-72806-1, 7.2.1-69057-6, 7.2-64570-4 and 7.1.1-42962-7.
- Synology-SA-24:23: BeeStation OS 1.0 and 1.1 are fixed in 1.1-65374.
- Exploitation status: CISA (@CISAgov) added CVE-2024-10441 to its KEV catalog on November 18, 2026, with a due date of November 21, 2026 for US federal agencies. Known ransomware use: Unknown. CISA's entry asks for forensic triage. CISA SSVC in the CVE record, November 19, 2026: Exploitation active, Automatable yes, Technical Impact total.
- Synology titles its DSM advisory PWN2OWN 2024. Rapid7 presented the research at DEF CON 33. This page does not link to exploit code.
- Synology and CISA name CWE-116; Rapid7 names CWE-141. The fix is the same.
What IntegrityLab.ai can check
- This advisory does not mean IntegrityLab.ai detects CVE-2024-10441.
- When enabled for an authorized assessment, IntegrityLab.ai's discovery records reachable web services and the server name they return. This gives your administrator a starting point. It does not currently offer a validated check for this CVE, a sign-in page test, confirmation of the installed build, or proof of compromise.
- A displayed Synology name or sign-in page is a clue, not proof of the installed build. A missing one does not rule a NAS out.