Synology says a remote attacker can read or write arbitrary files or cause denial of service. Its CVSS 3.1 vector requires neither credentials nor user interaction.Synology published advisory SA-26:21 on 19 November 2026 and still marks its response ongoing. The company lists DSM and BeeStation OS 1.5 as affected. It recommends deactivating the OAuth Service package while the listed fixes are pending. A vulnerability intelligence platform can help track the advisory, but administrators must verify each device's branch and running build.
What it allows
How Can CVE-2026-120382 Affect DSM?
Synology classifies the OAuth API flaw as CWE-88, improper neutralization of argument delimiters in a command. Its advisory does not publish a request sequence or identify which files an attacker could access. The defensible attack chain is network access to an affected API, the argument-handling flaw, then arbitrary file read or write or denial of service. This sequence is our reading of Synology's description, not a demonstrated exploit procedure.
The vendor's CVSS vector lists no required privileges or user interaction. Arbitrary file access raises confidentiality and integrity concerns; denial of service affects availability. These are possible outcomes in Synology's advisory, not evidence that a particular device has been compromised.
What Should Defenders Check Now?
Prioritize reachable DSM systems and BeeStation OS 1.5 devices, especially where the OAuth Service package is active. This priority order is our operational reading of Synology's network vector, affected-product list and mitigation. Confirm package state and full DSM build for each device before a change window.
Review OAuth Service access records, unexpected file changes and service interruptions on affected systems. Treat these as general investigation leads, not a vendor detection signature or proof of CVE-2026-120382 exploitation. Keep this flaw separate from the authenticated DSM Sharing API path traversal flaw, which has different prerequisites.
Who is affected
Which DSM and BeeStation Versions Are Affected by CVE-2026-120382?
Synology lists DSM 7.4, 7.3, 7.2.2, 7.2.1 and 7.1 as affected, along with BeeStation OS 1.5. Its detailed description also names DSM releases before 6.2.4-25556-9. For the listed DSM lines, the description gives thresholds of 7.1.1-42962-10, 7.2.1-69057-14, 7.2.2-72806-11, 7.3.2-86009-6 and 7.4.1-90080-2. Record the entire running build, including its update suffix.
The availability table marks BeeStation OS 1.5, DSM 7.2.2, 7.2.1 and 7.1 as ongoing. It recommends moving the two DSM 7.2 lines to 7.3.2-86009-6 or later. It schedules the DSM 7.3 and 7.4 fixed releases for 20 November 2026; as of 19 November, do not assume those builds can be installed. The advisory does not give BeeStation OS 1.5 a fixed build or release date.
Synology marks APM 1.2, APM 2.0, DSM Enterprise 1.0, SRM 1.2 and SRM 1.3 as unaffected. Its explicit mitigation for affected installations is to deactivate the OAuth Service package. Check package state after the change, then follow the advisory for release availability.
Once a branch-matched fix is published and installed, verify the running build and service health. Keep the update and verification record in your patch management process.
Timeline
- 2026-11-19
Synology published SA-26:21, rated CVE-2026-120382 Critical and marked affected product fixes ongoing. It scheduled DSM 7.3 and 7.4 fixed builds for release by 20 November.
What to do
-
Inventory DSM and BeeStation devices
Record each device's product, DSM or BeeStation branch, complete running build and OAuth Service package state. Compare it with Synology SA-26:21.
-
Deactivate OAuth Service while fixes are pending
Synology names deactivation of the OAuth Service package as its mitigation. Plan for any dependent sign-in workflows, then verify the package is inactive.
-
Track branch-specific release availability
Recheck Synology's advisory before scheduling an upgrade. It lists DSM 7.3.2-86009-6 and 7.4.1-90080-2 as scheduled by 20 November, while older lines and BeeStation OS 1.5 remain ongoing.
-
Install and verify an available fix
When Synology publishes the applicable build, install it and confirm the full running version on every affected device. Check OAuth-related service health after maintenance.
-
Review local evidence of abnormal activity
Inspect access records, unexpected file changes and service interruptions on affected devices. This is a Brandefense triage suggestion, not a Synology detection rule.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-120382 in Brandefense Atlas
The Atlas record of CVE-2026-120382: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Does CVE-2026-120382 require a DSM account?
Synology's CVSS 3.1 vector has PR:N and UI:N, meaning no privileges or user interaction are required in its assessment.
Are the DSM 7.3 and 7.4 fixes available on 19 November?
Synology schedules their fixed builds for release by 20 November 2026. Its advisory still marks the response ongoing on 19 November.
What can administrators do before a fix is released?
Synology advises deactivating the OAuth Service package. Confirm the package is inactive and monitor the advisory for branch-specific fixes.
Is BeeStation OS 1.5 covered by a fixed build?
Synology lists BeeStation OS 1.5 as affected and ongoing. The advisory gives no fixed build or release date for it.