Synology warns that an OAuth API flaw lets remote attackers read or write arbitrary files and disrupt service. Its November 19 advisory identifies CVE-2026-120382 in DiskStation Manager, the operating system for its network storage devices. Deactivate the OAuth Service package while arranging the applicable security update.

The repair status varies by branch. Synology’s November 20 revision now lists fixes for DSM 7.3 and 7.4, while several older branches remain Ongoing. Check the update offered for the exact device before restoring the affected service.

Update — November 20, 2026, 04:42 EST

Synology’s second advisory revision, updated at 16:25:36 UTC+8, changes the fix status for DSM 7.3 and 7.4. It removes the scheduled-release wording and now directs users to 7.3.2-86009-6 and 7.4.1-90080-2 or above, respectively.

The earlier version of this page described those two repairs as planned. That status has changed. DSM 7.1, 7.2.1, 7.2.2 and BeeStation OS 1.5 remain Ongoing, and the vendor still says to deactivate OAuth Service. The general DSM release-notes page still shows older builds, so verify the package offered for the specific model.

The exposed service matters alongside the device version

Synology describes an argument-handling flaw in the OAuth API. OAuth supports delegated access between applications. The vendor rates this issue as remotely reachable, requiring no existing privileges or user interaction.

An attacker needs a network path to the affected API. Publicly reachable management services therefore deserve immediate attention. Restricting them to trusted networks reduces reachability, but an internal location alone does not remove the flaw.

Evidence status: vendor-confirmed vulnerability, with no in-the-wild exploitation or public demonstration identified in the advisory. The severity rating describes possible impact and attack conditions, not a measured number of compromised devices.

Match the repair status to the branch

At review, Synology’s affected-product table lists:

Product or branch Vendor-listed response
DSM 7.4 7.4.1-90080-2 or above, listed as the fix in revision 2
DSM 7.3 7.3.2-86009-6 or above, listed as the fix in revision 2
DSM 7.2.2 and DSM 7.2.1 Ongoing; upgrading to 7.3.2-86009-6 or above is recommended
DSM 7.1 Ongoing
BeeStation OS 1.5 Ongoing

Synology marks APM 1.2 and 2.0, DSM Enterprise 1.0, and SRM 1.2 and 1.3 as unaffected.

The advisory’s detailed vulnerability paragraph also names older branch thresholds: 6.2.4-25556-9, 7.1.1-42962-10, 7.2.1-69057-14 and 7.2.2-72806-11. Those numbers appear alongside the newer DSM thresholds, while the availability table still says Ongoing. Treat them as vendor-listed vulnerability boundaries, not confirmation that packages have shipped.

The DSM release notes still showed 7.4.1-90080 Update 1 as their newest 7.4 entry during the November 20 follow-up. Follow the current advisory and the download offered for the exact model. Older hardware may have a different supported upgrade path.

Stop the service, then verify the repair path

Synology’s immediate mitigation is explicit: “Deactivate the OAuth Service package.” This reduces exposure through the affected component while repair availability remains unsettled.

For an operator, the next steps are:

  • Deactivate the package and account for applications that depend on it. Keep a trusted administrative access path available while assessing service impact.
  • Restrict management access to approved clients. A VPN, an encrypted private-network connection, can reduce public exposure. It complements the vendor mitigation and eventual patch.
  • Check the exact model, branch and offered update. Install the applicable repair when available, then verify the running build before restoring the affected service.
  • Keep recovery copies separate from the storage appliance. Arbitrary file writing threatens the data the device stores, including backups reachable through the same system.

This advisory describes a different flaw from the older Synology ransomware warning. Reports of attacks against that older vulnerability do not establish exploitation of CVE-2026-120382.

What the thread adds

The Hacker News discussion adds a concrete interface path. NathanKP writes: “Mitigation for now is to go to Package Center -> Installed -> OAuth Service and stop it.” The vendor advisory supports deactivating the package; the navigation detail comes from this commenter.

dj68k reports still serving data from an 1813+ running DSM 7.1.1-42962 Update 9 and questions future update availability. That self-report highlights why checking a model’s supported branch matters. It provides no evidence that the commenter’s device was compromised.

From a 6-comment thread, in HN’s own order.

Caveat: The advisory remains Ongoing for several branches; the new 7.3 and 7.4 fix status does not establish a completed rollout to every model.