Synology published advisory Synology-SA-26:19 on November 10, 2026. It covers a Critical flaw in DiskStation Manager, CVE-2026-76954, scored 9.8 on CVSS 3.1. The bug is a SQL injection in the Auth API, the component that decides whether you get to log in.
The fix is a DSM update. Synology lists no mitigation, so there’s nothing to toggle instead of patching.
What the advisory says
Synology describes CVE-2026-76954 as an improper neutralization of special elements used in an SQL command in the Auth API. The published vector is AV:N/AC:L/PR:N/UI:N. In plain terms: reachable over the network, low complexity, no privileges required, no user interaction. Per the advisory, remote attackers could read or write arbitrary files and cause denial of service.
The same advisory lists a second flaw, CVE-2026-85101, an authentication bypass in rsync scored 8.6 and rated Important. It allows reading specific files, writing arbitrary files and limited denial of service.
The fixed builds are:
- DSM 7.4: 7.4.1-90080-1 or above
- DSM 7.3: 7.3.2-86009-5 or above
- DSM 7.2: 7.2.2-72806-10 or above, or 7.2.1-69057-13 or above
That last line matters. Plenty of people stay on older branches on purpose. Synology still shipped 7.2 fixes, so there’s no reason to sit on an old build for this one.
A second advisory landed the same day
Synology also released Synology-SA-26:18, rated Important, covering 25 CVEs in DSM. The top of that list includes three scored 8.8: an authorization bypass in SSOAuth, a path restriction flaw in the Sharing API and a missing authentication step in the Auth API. It’s fixed in the 7.4 and 7.3 builds above, and Synology again lists mitigation as none.
Together that’s 27 flaws across two advisories. Security site SecurityOnline reports that Synology states no workarounds exist for either report, and that neither source it checked confirms active attacks or public exploit code. That’s a snapshot, not a promise. A 9.8 with a named component and a public advisory is exactly what people reverse engineer from the patch.
Why it matters for a home NAS
A NAS holds the data people care about most: photos, backups, documents, often the only copy of something. A flaw in the login path is the worst place for one, because the vector says no privileges are required. An attacker doesn’t need stolen credentials. They only need the service to be reachable.
Reachable is the part you control. If DSM’s web interface is forwarded through your router, it’s on the list of things scanners find. If it’s only on your LAN or behind a VPN, an attacker first needs a foothold inside, which is a much taller order. The patch still matters in that case. A compromised laptop or a cheap IoT gadget on the same network turns “LAN only” into “reachable.”
The rsync flaw is easy to forget about. People enable rsync for backups from another box once and then never think about it again. If you did, check whether that service is on and whether it’s reachable from anywhere it shouldn’t be.
What to do
- Open Control Panel, then Update & Restore, and install the build for your branch from the list above.
- Check the router for ports forwarded to the NAS.
- Turn off rsync and any other service you don’t actively use.
Where we land
We run a Synology NAS here, and the rule is simple: it doesn’t face the internet. Remote access goes over a VPN, not a forwarded port. That’s why a 9.8 in the login code is a “patch tonight” problem and not a “go find out who got in” problem.
The tradeoff is real. A VPN is one more thing to maintain, and it’s less convenient than typing a URL on your phone. Forwarding a port is easier. But then every bug in the login page is your problem the day it’s published, and this advisory shows what that costs when the bug needs no credentials.
If you only do one thing, patch. If you can do two, take the web interface off the internet. Synology’s own advisory says the update is the only remediation.