homelab

Two 9.8s in Synology DSM, and why a NAS is the worst thing to leave unpatched

Synology patched eight DSM vulnerabilities on September 18, two of them at CVSS 9.8. Singapore’s Cyber Security Agency put out an alert about them five days later, which is usually a sign the severity is being taken seriously somewhere other than the vendor’s own advisory page.

If you run a Synology and haven’t updated DSM since mid-September, that’s tonight’s job.

A Synology DiskStation NAS unit
A Synology DiskStation NAS. Photo: DYVER, CC BY-SA 4.0.

The versions

Synology rates the whole advisory Critical. Upgrade to whichever line you’re on:

  • DSM 7.4 → 7.4-90075 or later
  • DSM 7.3 → 7.3.2-86009-4 or later
  • DSM 7.2.2 → 7.2.2-72806-9 or later
  • DSM 7.2.1 → 7.2.1-69057-12 or later

No mitigation is offered, so updating is the whole of it.

What’s in it

Eight CVEs, four of them serious:

  • CVE-2026-13684 and CVE-2026-13639, both Critical at CVSS 9.8.
  • CVE-2026-13673 at 8.8 and CVE-2026-6205 at 8.1, both rated Important.
  • Four more rated Moderate or Low.

The underlying causes are worth reading as a group: insufficient entropy in login logic, improper output encoding in SCGI, incorrect permission assignment in the LDAP API, and external control of file names in the Upload API. Between them they allow a remote attacker to read or write arbitrary files, or cause denial of service.

“Insufficient entropy in login logic” is the one that should make you sit up. Entropy problems in authentication mean something that was supposed to be unguessable is more guessable than intended, and that’s a class of bug where the fix is the only option, because no configuration change makes a predictable value unpredictable.

Arbitrary file write on a NAS

Worth being specific about why this matters more on a NAS than it would elsewhere.

A NAS is where the backups live. Arbitrary file write on the box holding your backups is not the same as arbitrary file write on a laptop, because the backup is the thing you were going to use to recover from everything else.

It’s also the box most likely to be quietly out of date. Nobody logs into their NAS daily. It sits in a cupboard doing its job, and that’s exactly the property that makes an eight-week-old critical patch plausible on it.

While you’re in there

Three things worth checking on a box you’ve just remembered exists:

Turn on automatic DSM updates if they’re off. Control Panel, Update & Restore. There’s a real argument against auto-updating things that could break, and it loses to the argument that you demonstrably weren’t going to check manually.

Check whether anything is reachable from outside. If QuickConnect is on or ports are forwarded, these CVEs went from “someone on my network” to “anyone”. We wrote a guide on the alternative.

Confirm your backups actually ran. Not that they’re configured. That they ran, recently, and that you’ve restored from one at some point. The backups guide covers the difference between the two tools and why you want both.

Where we land

Nothing unusual happened here. A vendor found serious bugs, patched them, published an advisory, and a national CSIRT amplified it. That’s the process working.

The part that doesn’t work is the appliance model. A NAS is sold as a thing you set up once and forget, and the forgetting is the entire security problem. Every property that makes it convenient, that it’s always on, that it holds everything, that it needs no attention, also makes it the worst thing on your network to leave three patches behind.

Sources: Synology’s advisory SA-26-13 with the fixed versions, Singapore CSA’s alert.

root@labs:~$ subscribe

New posts, once a week

One email on Sunday morning with what we published that week. No tracking pixel, and unsubscribing is one click.

Leave a comment

Your email address will not be published. Required fields are marked *