Synology DSM hit by critical 9.8 flaw allowing remote file read and write

Synology Security Advisory

Synology has disclosed CVE-2026-120382, a critical command-injection flaw in the OAuth API of DiskStation Manager, scoring 9.8 on the CVSS scale. Unauthenticated remote attackers can read or write arbitrary files and launch denial-of-service attacks. Nearly every DSM branch from 7.1 through 7.4 is affected, with BeeStation OS 1.5 also critical. Fixes for DSM 7.4 and 7.3 are due by November 20, 2026; until then, Synology advises deactivating the OAuth Service package.

An improper neutralization of argument delimiters in a command vulnerability in the OAuth API in Synology DiskStation Manager (DSM) allows remote attackers to read or write arbitrary files and conduct denial-of-service attacks.
  1. RetroTechie

    I've always wondered: if you take the cause of each CVE, look at underlying cause of that & repeat, how many essential root problems would you be left with?

    "Can't do math" (off-by-1 errors etc)

    "Sanitize your inputs" (escape sequences, parsing etc)

    "What are you referencing?" (null pointers, use-after-free etc)

    and error handling. Plain error codes bubbling up a call stack, or bypassing that somehow which may violate program structure.

    How many of these fundamental issues are there?

  2. SchemaLoad

    You just can't have a NAS exposed to the internet. Put it behind a VPN or you will have it hacked.

  3. 6thbit

    Tied to this weakness:

    > CWE-88: Improper Neutralization of Argument Delimiters in a Command

    So, they were building shell commands from some kind of user input in the OAuth API?

  4. mattbee

    If you've got an ancient unit like mine where the fix status is "Ongoing" :/ Synology's advised mitigation is to "Remove the OAuth Service Package", i.e. find it from the Package Centre off the main menu, and click Uninstall.

    I've never used OAuth, it looked completely unconfigured. But it's the subject of this CVE and seems to be installed by default .

  5. NathanKP

    Mitigation for now is to go to Package Center -> Installed -> OAuth Service and stop it.

More from this day

2026-11-19