Published 22 November 2026 · Rathish Kumar, Invitty
Synology published advisory Synology-SA-26:21 on 19 November 2026 for CVE-2026-120382, a critical flaw (CVSS 9.8) in the DSM OAuth API that lets a remote attacker with no login read or write files and crash the NAS. On 20 November it shipped fixes: DSM 7.4.1-90080-2 and DSM 7.3.2-86009-6. Older DSM trains are still waiting. Upgrade now if you can, and deactivate the OAuth Service package if you cannot.
What is CVE-2026-120382?
Synology classes it as CWE-88, improper neutralisation of argument delimiters in a command. In plain terms, input sent to the OAuth API can be shaped so that a command on the NAS runs with arguments the attacker chose. The CVSS vector is network reachable, low complexity, no privileges and no user action, with high impact on confidentiality, integrity and availability. That combination is why it scores 9.8.
Arbitrary file write on a NAS is the part that worries me. Many of the Synology boxes we look after in Chennai and Bangalore hold the only on-site copy of file shares and backups. If someone can write files there, they can damage the data you rely on to recover from every other incident.
Synology released a second advisory the same day, Synology-SA-26:20, nicknamed NGINX2Root. It tracks CVE-2026-123007 (CVSS 8.1), an HTTP/2 heap overflow in the NGINX web server that DSM uses. The same two DSM builds close both flaws.
Which DSM versions are affected, and which builds fix them?
| Product | Status for CVE-2026-120382 |
|---|---|
| DSM 7.4 | Fixed: upgrade to 7.4.1-90080-2 or later |
| DSM 7.3 | Fixed: upgrade to 7.3.2-86009-6 or later |
| DSM 7.2.2 and 7.2.1 | Fix ongoing; Synology recommends moving to 7.3.2-86009-6 |
| DSM 7.1 | Fix ongoing |
| BeeStation OS 1.5 | Fix ongoing |
| DSM Enterprise 1.0, SRM 1.2 and 1.3, APM 1.2 and 2.0 | Not affected |
One oddity: the CVE description in the advisory also names build numbers for older trains, such as 7.2.2-72806-11 and 7.1.1-42962-10. The product table still marks those trains as ongoing. Until Synology updates the table, treat DSM 7.1 and 7.2 as unpatched and check Package Center or the download page for the exact build before you rely on it.
For the NGINX flaw, DSM Enterprise 1.0 and both APM versions are affected as well, with fixes still pending.
How do you check your NAS?
- Sign in to DSM and open Control Panel, then Info Center. The General tab shows the model and the exact DSM version and build.
- Compare that build with the table above. A DSM 7.3 or 7.4 unit below the fixed build needs the update now.
- Open Package Center and see whether the OAuth Service package is installed and running. If nothing in your setup uses DSM as a sign-in provider for other apps, it is often installed but idle.
- Check whether DSM is reachable from the internet through port forwarding, QuickConnect or a reverse proxy. An exposed management page moves this from "this week" to "today".
What should you do, in order?
- Take a fresh backup of anything critical to a second device or the cloud before touching firmware. A NAS update rarely fails, but a failed one on a single copy of data is painful.
- DSM 7.3 and 7.4: install 7.3.2-86009-6 or 7.4.1-90080-2 through Control Panel, Update and Restore. Plan a reboot window.
- DSM 7.2.1 and 7.2.2: Synology points you to 7.3.2-86009-6. Check that your model supports DSM 7.3 and that the packages you depend on have 7.3 versions first.
- DSM 7.1, BeeStation, or any unit you cannot reboot this week: deactivate the OAuth Service package, and disable HTTP/2 under Control Panel, Network, Connectivity to cover the NGINX flaw.
- Remove direct internet exposure of the DSM login page. Put remote access behind your firewall VPN instead.
Logging matters for regulated businesses too. If you find signs that a NAS was accessed without authorisation, CERT-In expects the incident reported within 6 hours of noticing it.
Why this matters more than a routine NAS update
Synology warned customers in late October that ransomware operators were encrypting NAS units running outdated DSM. The Hacker News reported on 3 November that the C3RB3R group had used older DSM flaws to lock files with a .L0CK3D extension. None of that involved this new CVE. It does show that attackers already scan for unpatched Synology devices, and a fresh 9.8 with file write is exactly what they look for.
A trade report on 19 November also mentioned a public proof-of-concept for the NGINX flaw. We have not confirmed that on Synology's own pages, but it is another reason to close both issues in one upgrade.
What it means for budgets and replacement plans
If your NAS is too old for DSM 7.3, this advisory is a good test of how long you want to wait for back-ported fixes. My view: any unit that cannot move to 7.3 and holds business data should go into next quarter's budget for replacement, with the old box kept only as a secondary copy. Ask for the replacement and any extra drives on a GST invoice so the input credit is clean.
Next step
We supply and support Synology NAS units and can read your model and DSM build, plan the update window and set up a second copy before you patch. If the box is due for replacement, see our Synology backup and storage options, and our firewall team can move remote NAS access behind a VPN.
Questions about the Synology DSM flaw
Is my Synology NAS affected by CVE-2026-120382?
Which DSM build fixes CVE-2026-120382?
Is there a workaround if I cannot upgrade yet?
Is CVE-2026-120382 being exploited?
Not sure if your devices are affected? Send us the model and current firmware or version through our chat assistant, or use the form on this page. We will tell you whether this advisory applies to you and which update to schedule.
Sources
Facts in this post come from these pages, checked on 22 November 2026. Advisories change, so confirm the current fix status on Synology's site before you act.
- Synology-SA-26:21 DSM, BeeStation OS: CVE-2026-120382 (published 19 November 2026, revised 20 November 2026)
- Synology-SA-26:20 NGINX2Root: CVE-2026-123007 (published 19 November 2026, revised 20 November 2026)
- Daily CyberSecurity: Synology DSM vulnerabilities, CVE-2026-120382 and CVE-2026-123007 (19 November 2026)
- The Hacker News: Synology NAS devices targeted in ransomware attacks (3 November 2026)