Technology

Synology warns of critical file-access flaw in DSM and BeeStation OS, with fixes still rolling out

Martin HollowayPublished 2m ago4 min readBased on 2 sources
Reading level
Synology warns of critical file-access flaw in DSM and BeeStation OS, with fixes still rolling out
source:synology.com

Synology has published Security Advisory SA-26-21, dated 2026-11-19, covering CVE-2026-120382. The flaw allows remote attackers to read or write arbitrary files and to carry out denial-of-service (DoS) attacks, which knock a service offline by overwhelming it. The advisory is Revision 1, the first public release, so its wording may change as remediation progresses.

The advisory lists DSM 7.1, DSM 7.2.1, DSM 7.2.2, DSM 7.3, DSM 7.4 and BeeStation OS 1.5 as critically affected. DSM is Synology's operating system for its network-attached storage (NAS) devices. It lists APM 2.0, APM 1.2, DSM Enterprise 1.0, SRM 1.3 and SRM 1.2 as not affected. For fleet audits the split matters: DSM Enterprise and SRM fall outside this advisory, while every consumer and small-business (SMB) DSM branch in the current support matrix is inside it.

Fix status varies by branch. Synology states that the DSM 7.4 fix, an upgrade to 7.4.1-90080-2 or above, and the DSM 7.3 fix, an upgrade to 7.3.2-86009-6 or above, are scheduled for release by 2026-11-20. These are scheduled dates, not shipped builds. For BeeStation OS 1.5, DSM 7.2.2, DSM 7.2.1 and DSM 7.1, the fix status reads OnGoing. For DSM 7.2.2 and 7.2.1, the advisory recommends upgrading to 7.3.2-86009-6 or above rather than waiting for a branch-specific patch.

The interim mitigation is to deactivate the OAuth Service package. OAuth is a standard for delegated sign-in authorisation, so the package is one that a device may use to grant access to apps and services. Administrators have to take the mitigation at the vendor's word on scope.

Synology's security pages describe how the company handles reports and disclosure. It offers an online form for reporting security issues in its products and a Product Security PGP key for encrypting sensitive details. The company says it monitors submissions to identify potential product security issues and will not reply unless it needs further information. Technical support questions go to its Support & Service section, not the security form. Synology says it does not publicly announce vulnerabilities, or release exact details of them, until fixes are publicly available, and then announces the vulnerability on its official website. That policy explains why the advisory carries the impact statement and version matrix without a technical write-up.

In my view, the practical question for operators on DSM 7.1, 7.2.x and BeeStation OS 1.5 is timing rather than the version table. Where the fix status reads OnGoing, the only documented action is the OAuth Service deactivation, and that step helps only those who can tell whether the package is running on their units. Inventorying installed packages, not just firmware versions, is the first job for an administrator on those branches.

The broader context here is a familiar one for NAS and small-server platforms. These devices often sit on home or small-office networks with remote access enabled for convenience, so exposure follows from that configuration as much as from the code. A vendor that publishes a single named upgrade target per branch, as Synology does for DSM 7.3 and 7.4, makes the response manageable for operations teams. The version matrix is short and the mitigation is one documented step, which gives administrators something concrete to act on while the remaining fixes are finalised.

The scheduled 2026-11-20 release date is the next checkpoint for the DSM 7.3 and 7.4 branches. Administrators should track the advisory page for revisions, since the company's stated policy is to publish details only once fixes are generally available.