CVE-2026-120382, an undisclosed bug in the OAuth API that scores 9.8 on the CVSS 3.1 scale. Per the vendor, a remote attacker needs no login and no user interaction to read or write arbitrary files or trigger a denial of service.
The second, Synology-SA-26:20, covers CVE-2026-123007, Synology’s implementation of the NGINX HTTP/2 flaw disclosed as part of the wider NGINX2Root set. It is rated Important with a CVSS score of 8.1. Synology says it has seen no exploitation of either bug in the wild, and neither appears in the CISA Known Exploited Vulnerabilities catalog.
One Bug Needs No Login, the Other Has a Public Exploit
The two flaws work very differently. CVE-2026-120382 is classed as CWE-88, improper neutralization of argument delimiters in a command. The OAuth Service package lets third-party apps get token access instead of handling user passwords, and an attacker can abuse that argument injection to manipulate internal system files without credentials. The attack runs over the network.
CVE-2026-123007 is a flow-control problem. When NGINX handles crafted HTTP/2 traffic that pushes the flow control window past allowed limits, it triggers a heap buffer overflow that crashes worker processes. F5 and the NGINX project shipped upstream patches on , and Synology folded fixes into its own builds. Rapid7 has since published proof-of-concept code that hits the flaw in local Docker containers running NGINX 1.31.8, though remote exploitability against a default DSM install is conditional.
Patches Cover Two Branches, Everyone Else Gets Workarounds
Synology released DSM 7.4.1-90080-2 and DSM 7.3.2-86009-6 to its download archive between and . Older branches are still waiting.
| Product | SA-26:21 (OAuth API) | SA-26:20 (NGINX HTTP/2) |
|---|---|---|
| DSM 7.4 | Upgrade to 7.4.1-90080-2 or above | Upgrade to 7.4.1-90080-2 or above |
| DSM 7.3 | Upgrade to 7.3.2-86009-6 or above | Upgrade to 7.3.2-86009-6 or above |
| DSM 7.2.2 | Ongoing (upgrade to 7.3.2-86009-6 or above recommended) | Ongoing (upgrade to 7.3.2-86009-6 or above recommended) |
| DSM 7.2.1 | Ongoing (upgrade to 7.3.2-86009-6 or above recommended) | Ongoing (upgrade to 7.3.2-86009-6 or above recommended) |
| DSM 7.1 | Ongoing | Ongoing |
| BeeStation OS 1.5 | Ongoing | Ongoing |
| DSM Enterprise 1.0 | Not affected | Ongoing |
| APM 2.0 and APM 1.2 | Not affected | Ongoing |
| SRM 1.3 and SRM 1.2 | Not affected | Not affected |
For anything not yet patched, Synology advises two stopgaps:
- Disable the OAuth Service package entirely to block the API flaw
- Turn off HTTP/2 in the Network connectivity control panel to close the NGINX route
Devices exposed to the internet through port forwarding or a reverse proxy stay at the highest risk until a patch is installed manually or rolled out in the owner’s region.
Hashlytics Take
The 9.8 is what gets the headlines, but the table is the real story. Only two DSM branches have a fix for either bug today, and everyone on 7.2, 7.1 or BeeStation OS is leaning on a toggle in a control panel. That is a thin defense for a device that usually holds backups and sits behind a forwarded port. There is also an awkward gap in the evidence: the lower-rated NGINX flaw already has public proof-of-concept code, while the critical OAuth flaw does not. That will not last, and anyone who has not disabled OAuth Service or upgraded by the time details surface will be racing someone else’s script.
Follow Hashlytics on Bluesky, Facebook, LinkedIn , Telegram and X to Get Instant Updates

