SystemsCritical 9.8In CISA KEVPatch available
CVE-2024-10441
Remote code execution in Synology DSM/BSM system plugin daemon.
How scary is it?
updated 19 Nov 2026- Yes
Works without logging in1
No account and no user action needed (CVSS PR:N, UI:N).
- Yes
Reachable over the network1
Can be attacked remotely (CVSS AV:N).
- Yes
Proof-of-concept code is public2
2 GitHub proofs of concept. GitHub proofs of concept are unvetted: some are fake or carry malware. No Exploit-DB entry or Metasploit exploit module on record.
- Yes
Attacks seen in the wild3
CISA lists it as exploited in the wild.
- Yes
On CISA's exploited list (since 18 Nov 2026)3
CISA deadline for US federal agencies: 21 Nov 2026.
Scare-o-meter
Drop everything
Attackers are already on it. Patch now.
- Low signal
- Routine patch
- Act this week
- Drop everything
Why: Listed in CISA's Known Exploited Vulnerabilities catalog: it is being used in attacks.3 Read from the same rule that decides our alert emails.
Are you affected? only if all are true
You run one of these 2 products in an affected versionSynology BeeStation OS (BSM) / Synology DiskStation Manager (DSM)
Synology BeeStation OS (BSM): >= 1.1 and < 1.1-65374, >= 1.0 and < 1.1-65374, < 1.0
Synology DiskStation Manager (DSM): >= 7.2.2 and < 7.2.2-72806-1, >= 7.2.1 and < 7.2.1-69057-6, >= 7.2 and < 7.2-64570-4, >= 7.1 and < 7.1.1-42962-7 (+1 more)
As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.
See the affected products table · Source 1
An attacker can reach it over the network
CVSS attack vector: Network (AV:N). Reachable over the internet or any routable network.
Source 1
Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.
What to do
Per our analysisA patch is available
The CVE record we hold states no fixed release number. See the advisories in the references.
CISA required actionApply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing…
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA's required action for this KEV entry, due 21 Nov 2026 for US federal agencies.
Source 3
Recommendation, AI-writtenApply Synology security updates immediately; isolate internet-exposed NAS until patched.
Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.
Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.
Major vulnerability. CISA KEV-listed remote RCE in widely deployed Synology DSM/BSM NAS; active exploitation risk and high CVSS (9.8) — organization-wide attention required.
- CVSS
- 9.8Criticalscored by the publisher (CNA)
- Exploited in the wild
- Yes, in CISA KEV since 18 Nov 2026CISA deadline for US federal agencies: 21 Nov 2026unvetted proof-of-concept code on github
- EPSS
- 3.1%chance of exploitation in the next 30 daystop 12% of scored CVEsFIRST score of 21 Nov 2026
- Fix
- Patch availablesee the advisories in the references
- Published
- 19 Mar 2025analysed here 19 Nov 2026
Do first. Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. (CISA's required action for this KEV entry)
Summary
Impact
Remote arbitrary code execution via improper output encoding; attackers can gain full system control, steal data, deploy ransomware, or maintain persistence.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| Synology BeeStation OS (BSM) | >= 1.1 and < 1.1-65374>= 1.0 and < 1.1-65374< 1.0Vendor says fixed in: not stated | |
| Synology DiskStation Manager (DSM) | >= 7.2.2 and < 7.2.2-72806-1>= 7.2.1 and < 7.2.1-69057-6>= 7.2 and < 7.2-64570-4>= 7.1 and < 7.1.1-42962-7< 7.0Vendor says fixed in: not stated |
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.
Products named in our analysis
- Synology BeeStation OS (BSM) 1.0, 1.0.1, 1.0.2, 1.1 (prior to 1.1-65374)
- Synology DiskStation Manager (DSM) versions prior to 7.2-64570-4, 7.2.1-69057-6, 7.2.2-72806-1
Fix and mitigation
Action required
Immediate action required
WAF and other mitigations
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Listed since 18 Nov 2026.
- CISA due date
- 21 Nov 2026, the remediation deadline for US federal agencies
- CISA required action
- Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
- Public exploit code
- Unvetted proof-of-concept code on GitHub: 2 GitHub proofs of concept
- CISA SSVC
- exploitation active, automatable yes, technical impact totalAssessed by CISA 18 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
GitHub proofs of concept
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
Timeline
- 19 Mar 2025Published
- 25 Oct 2026First proof-of-concept repository on GitHub (unvetted)585 days (about 2 years) later
- 18 Nov 2026Added to CISA KEV (exploited in the wild)24 days later
- 18 Nov 2026CISA SSVC assessment: exploitation activesame day later
- 19 Nov 2026CVE record last updated1 day later
- 19 Nov 2026Analysed by vulneraibility.comsame day later
- 21 Nov 2026CISA remediation due date (US federal agencies)2 days later
Common questions
Is CVE-2024-10441 being exploited?
Yes. CVE-2024-10441 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2024-10441?
CVE-2024-10441 is rated Critical with a CVSS score of 9.8. 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-2024-10441?
Yes. A fix has been recorded for CVE-2024-10441. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2024-10441 affect?
CVE-2024-10441 affects Synology BeeStation OS (BSM) 1.0, 1.0.1, 1.0.2, 1.1 (prior to 1.1-65374), Synology DiskStation Manager (DSM) versions prior to 7.2-64570-4, 7.2.1-69057-6, 7.2.2-72806-1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2024-10441?
Apply Synology security updates immediately; isolate internet-exposed NAS until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
3 references in the CVE record, grouped by the tags the record gives them.
Advisories (2)
- synology.com /en-global/security/advisory/Synology_SA_24_20
- synology.com /en-global/security/advisory/Synology_SA_24_23
Other links (1)
- cisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-10441
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.