Synology Discovers Critical Vulnerabilities in DiskStation Manager and BeeStation OS, Promises Timely Fixes
Synology has recently brought to light two significant vulnerabilities that have the potential to be remotely exploited, affecting its well-known DiskStation Manager (DSM) and the BeeStation OS. The company has announced that patches for both versions of DSM are set for release by November 20, 2026, a necessary step to mitigate risks associated with these security flaws.
In notices dated November 19, Synology identified a critical OAuth API vulnerability, designated as CVE-2026-120382, alongside an NGINX HTTP/2 memory corruption flaw, classified as CVE-2026-123007. Both vulnerabilities have been assigned a critical severity rating, with scores of 9.8 and 8.1, respectively, according to the Common Vulnerability Scoring System (CVSS). A notable aspect of these flaws is that they can be exploited without requiring an account or any form of user interaction, significantly increasing the urgency for users to address these issues.
In-Depth Analysis of the Vulnerabilities
The first vulnerability, CVE-2026-120382, is linked to the mishandling of command argument delimiters within the DSM OAuth API. This particular flaw allows a remote attacker to either read or write arbitrary files, potentially leading to a denial of service. As outlined in the security advisory, the complexity of executing this attack is relatively low, heightening the risks for affected systems. Unlike previous vulnerabilities related to Synology’s Network File System (NFS), which primarily permitted unauthorized file access, this new flaw amplifies the threat by enabling attackers to modify files directly. As an immediate measure, Synology has advised users to temporarily deactivate the OAuth Service package until a permanent fix is available.
In a related issue, CVE-2026-123007 pertains to a heap buffer overflow in both NGINX Plus and NGINX Open Source configurations utilizing HTTP/2. This memory corruption issue can lead to the crashing of an NGINX worker, and, in certain scenarios where the Address Space Layout Randomization (ASLR) is either disabled or can be circumvented, there could even be a potential for remote code execution. Unlike another distinct NGINX HTTP/2 vulnerability associated with upstream connections, this one concerns flow control mechanisms within HTTP/2.
To safeguard systems, Synology recommends that users disable HTTP/2 by navigating to Control Panel > Network > Connectivity. It’s crucial to note that both advisories indicate that DSM versions 7.1, 7.2.1, 7.2.2, 7.3, and 7.4, as well as BeeStation OS version 1.5, are susceptible to these vulnerabilities. While the NGINX flaw further impacts APM versions 1.2 and 2.0, as well as DSM Enterprise version 1.0, the OAuth vulnerabilities do not affect these specific products.
Recommended Actions for Users
In light of these vulnerabilities, administrators of affected systems should pay close attention to the specific DSM versions mentioned in the advisories, notably DSM 7.4.1-90080-2 and 7.3.2-86009-6. These versions represent the minimum fixed builds that will be made available by November 20. Synology advocates that users operating on older versions, specifically 7.2.1 and 7.2.2, upgrade to at least version 7.3.2-86009-6 to ensure protection against these vulnerabilities.
Though the OAuth advisory provides technical details regarding fixed version thresholds for older branches, users are cautioned that merely relying on version numbers does not guarantee immediate availability of updates. Administrators are encouraged to verify installed builds against the Synology Product Security Advisory portal, particularly for devices that connect to untrusted networks, to ensure their systems are adequately protected.
In scenarios where an immediate update is not accessible, it is advisable to implement the recommended workarounds. Disabling HTTP/2 will not resolve the OAuth flaw, and similarly, turning off the OAuth Service does not address the NGINX issue. As such, systems impacted by both vulnerabilities will need to utilize both mitigations while awaiting a reliable update. Once updates are installed, it is imperative to verify that the operating build is running correctly before restoring any disabled features.
In summary, the identification of these critical vulnerabilities is a call to action for users of Synology products. By taking necessary precautions and adhering to Synology’s guidance, administrators can significantly mitigate risks associated with these security flaws.

