Update log: Updated 2026-11-19: refreshed platform data.

Carrying a base score of CVSS 9.6, the Synology DiskStation Manager vulnerability tracked as CVE-2024-10441 entered the Known Exploited Vulnerabilities catalog on 2026-11-18. This vulnerability originally appeared in the National Vulnerability Database on 2025-03-19. The catalog addition represents a new confirmation of exploitation for an older, already-disclosed vulnerability. PurpleOps recorded 3 exploit-feed entries for the vulnerability. The first exploit-feed entry surfaced on 2025-04-01, which occurred 596 days before KEV listing.

Is CVE-2024-10441 being exploited?

The addition of CVE-2024-10441 to the catalog confirms active exploitation in the wild. The vulnerability affects the system plugin daemon in Synology DiskStation Manager and Synology BeeStation OS. The vulnerability is categorized under weakness class CWE-116. The Cybersecurity and Infrastructure Security Agency describes the vulnerability as an improper encoding or escaping of output. This specific failure allows a remote attacker to execute arbitrary code via unspecified vectors.

The vulnerability carries a severity vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. This metrics string establishes that the vulnerable service is reachable over the network. An attacker requires no privileges and no user interaction to complete the exploit sequence. The attack complexity remains low. Upon successful execution, the target system experiences a total loss of confidentiality, integrity, and availability. No indicators of compromise appear in the public reporting collected by PurpleOps, requiring defenders to use behavioral hunt leads instead.

Who is affected?

The National Vulnerability Database configuration data outlines the specific software builds vulnerable to remote code execution. The vulnerability appears in Synology BeeStation OS before version 1.1-65374 and Synology DiskStation Manager before versions 7.2-64570-4, 7.2.1-69057-6, and 7.2.2-72806-1.

Affected Product Version
Synology Beestation Os 1.0
Synology Beestation Os 1.0.1
Synology Beestation Os 1.0.2
Synology Beestation Os 1.1
Synology Diskstation Manager 7.2 up to, not including, 7.2-64570-4
Synology Diskstation Manager 7.2.1-69057 up to, not including, 7.2.1-69057-6
Synology Diskstation Manager 7.2.2 up to, not including, 7.2.2-72806-1

The table documents the complete range of affected operating system releases. Builds at or above a fixed version are not affected.

What should I patch first?

The required action for federal agencies mandates applying mitigations in accordance with vendor instructions. Agencies must complete this remediation by the due date of 2026-11-21. The instructions demand compliance with CISA BOD 26-04 Prioritizing Security Updates Based on Risk guidance. Organizations must also comply with the Forensics Triage Requirements published by the agency. Network administrators must follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable.

How do I detect it?

Because the public reporting omits indicators of compromise, defenders detect activity through behavioral hunt leads and system logs. Security teams require web or application access logs for the affected service, kept at full request detail. Visibility into exploitation also depends on outbound network connection logs from the hosts running the vulnerable service. Defenders collect process creation logs for the hosts running the service, relying specifically on Sysmon event 1 on Windows or auditd execve on Linux.

Analysts monitor for the service process starting an interpreter or shell. Additional hunt leads include files written into directories the service can execute, and outbound connections from the service host to addresses it has never contacted before.

If a hunt lead hits, responders capture the service logs and a memory image before restarting the service. Security teams rotate the credentials and tokens the service host held. They then compare the files of the service against a known-good deployment before returning the device to production.

The detection rule below identifies a web server or application server process starting a shell or scripting interpreter. Defenders tune the logic to avoid false positives by allow-listing the maintenance jobs that legitimately run under the service account, by command line.

title: Web Service Process Spawning a Shell or Interpreter
id: a50869ab-edeb-46b0-96ca-df4922bdb116
status: experimental
description: Detects a web server or application server process starting a shell or scripting interpreter, the first observable step after remote code execution in a web application.
logsource:
  category: process_creation
detection:
  selection_parent:
    ParentImage|endswith:
      - '\w3wp.exe'
      - '\httpd.exe'
      - '\nginx.exe'
      - '\java.exe'
      - '\node.exe'
      - '/httpd'
      - '/apache2'
      - '/nginx'
      - '/java'
      - '/node'
  selection_parent_php:
    ParentImage|contains: '/php-fpm'
  selection_child:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '/sh'
      - '/bash'
      - '/dash'
      - '/python3'
      - '/perl'
  condition: (selection_parent or selection_parent_php) and selection_child
falsepositives:
  - Application maintenance or deployment scripts launched by the web service account
level: high

PurpleOps data feeds into BUGSY to help security teams identify exploitation patterns across vulnerable applications. Read the PurpleOps blog for technical breakdowns of network vulnerabilities. Security teams operationalize these detection rules by visiting our AI analysts page.