Status: On November 19, 2026, Synology published two security advisories for the operating systems on its NAS devices. Synology-SA-26:21 covers CVE-2026-120382, a previously undisclosed flaw in the OAuth API of DiskStation Manager (DSM) and BeeStation OS that Synology says "allows remote attackers to read or write arbitrary files and conduct denial-of-service attacks." Synology scores it CVSS 3.1 9.8. Synology-SA-26:20 is Synology's fix for CVE-2026-123007, the NGINX HTTP/2 flaw that F5 and the nginx project disclosed on November 18 as part of the "NGINX2Root" set, in DSM, BeeStation OS, DSM Enterprise and Synology's APM operating system. On November 20 Synology revised both advisories to list the first fixed releases, DSM 7.4.1-90080-2 and DSM 7.3.2-86009-6. Fixes for DSM 7.2.2, 7.2.1 and 7.1 and for BeeStation OS 1.5 are still marked "OnGoing." Until a device is updated, Synology's temporary mitigations are to deactivate the OAuth Service package and to disable HTTP/2. Synology says that "no exploitation of these vulnerabilities has been observed." CVE-2026-120382 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. CVE-2026-123007 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. We checked catalogVersion 2026.11.20 at 15:41 EST and again at 15:44 EST on November 21, 2026. That catalog was released on November 20, 2026 at 12:48 EST and contains 1,790 entries. We last checked all sources between 15:41 and 15:49 EST on November 21, 2026.
Executive Summary
OAuth Service is a Synology package that lets third-party applications obtain access to DSM services through tokens instead of user passwords. Synology's release notes have described it as a "built-in package" since its first version. Synology's advisory places CVE-2026-120382 in the OAuth API and says a remote attacker can use it to read or write arbitrary files on the device and to cause a denial of service. Synology has not published the vulnerable endpoint, the command involved or any request pattern.
What matters for planning:
- No login is needed. Synology's CVSS vector for CVE-2026-120382 reads network attack vector, no privileges and no user interaction.
- The fix is a DSM update, not a package update. The fixed releases Synology names are DSM builds. The newest OAuth Service release in Synology's release notes is still 1.3.0-0220 of June 16, 2026 (Rescana's reading of the release notes).
- Only DSM 7.4 and DSM 7.3 have fixes so far. Synology recommends that DSM 7.2.2 and 7.2.1 users move to 7.3.2-86009-6. DSM 7.1 and BeeStation OS 1.5 have no fixed release yet, so the mitigations are the only protection on those devices today.
- The same two DSM builds also fix CVE-2026-123007. That flaw has public proof-of-concept code, which its authors describe as working only under narrow conditions. It is covered in depth in our NGINX HTTP/2 advisory.
- There is no report of exploitation. Synology says none has been observed, and we found no public exploit code for CVE-2026-120382.
Who should act first (Rescana guidance). Owners of Synology devices whose DSM or BeeStation web interface can be reached from the internet, through port forwarding, a reverse proxy or another remote access path; devices on DSM 7.1 or BeeStation OS 1.5, which have no fix yet; and suppliers that keep your files or your backups on a Synology NAS.
Technical Information
CVE-2026-120382, as Synology describes it. "An improper neutralization of argument delimiters in a command vulnerability in the OAuth API in Synology DiskStation Manager (DSM) before 6.2.4-25556-9, 7.1.1-42962-10, 7.2.1-69057-14, 7.2.2-72806-11, 7.3.2-86009-6, and 7.4.1-90080-2 allows remote attackers to read or write arbitrary files and conduct denial-of-service attacks." Synology gives the CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base score 9.8, and the weakness CWE-88, Improper Neutralization of Argument Delimiters in a Command. The advisory credits no reporter.
What CWE-88 means here (Rescana's summary). In an argument injection flaw, input that should become one value passed to a program is split into extra options or arguments. The program then does something its caller never intended, such as reading or writing a file it was not meant to touch. That fits the impact Synology lists. Synology does not say the flaw allows command execution, and we do not claim it. Arbitrary file writes on a storage device are serious on their own: the device holds the data, and some files on it control how the system behaves (Rescana's reading).
Builds named in the description but not yet published. The CVE description lists fixed builds for DSM 6.2.4, 7.1.1, 7.2.1 and 7.2.2 as well as the two releases now available. Synology's download archive at 12:19 EST on November 20, and again at 15:42 EST and 15:48 EST on November 21, had no 6.2.4-25556-9, 7.1.1-42962-10, 7.2.1-69057-14 or 7.2.2-72806-11; the newest builds in those lines were 6.2.4-25556-8, 7.1.1-42962-9, 7.2.1-69057-13 and 7.2.2-72806-10 (Rescana's reading of the archive). Synology's press release says updates "for other operating systems as well as certain end-of-life DSM versions are scheduled for upcoming releases." DSM 6.2 does not appear in the advisory's product table, but its build in the description suggests Synology treats it as affected (Rescana's reading).
No CVE record yet. CVE.org answered "The cve record for the cve id does not exist" for CVE-2026-120382, and the NVD API returned no results, at 12:16 EST and again at 12:18 EST on November 20, and again at 15:41 EST and 15:44 EST on November 21. Until a record appears, Synology's advisory is the only source for the score and the affected versions, and scanners that rely on NVD data may not flag the flaw yet (Rescana's reading).
CVE-2026-123007 in Synology products. SA-26:20 repeats F5's description of the NGINX flaw: when NGINX handles crafted HTTP/2 traffic, "the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault," and attackers "can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR." Synology labels CVE-2026-123007 "Important" with CVSS 3.1 8.1 and the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, the same 3.1 score F5 gives as the CNA. F5 also scores it 9.2 under CVSS 4.0. The abstract at the top of SA-26:20 uses the same "read or write arbitrary files" wording as SA-26:21; the detail section, which matches F5's CVE record, is the description to rely on (Rescana's reading). Synology's press release refers to "the NGINX2Root vulnerabilities" in the plural, but SA-26:20 names only CVE-2026-123007.
Exploitation and public code. Synology's press release says: "As of this announcement, no exploitation of these vulnerabilities has been observed." The KEV status of both CVEs is stated at the top of this post. CISA's enrichment on the CVE-2026-123007 record, dated November 18, rates exploitation "none," automatable "no" and technical impact "total." FIRST's EPSS service had no score for CVE-2026-120382. It gave CVE-2026-123007 a score of 0.29863 (98th percentile) on November 21; on November 20 the same service gave that CVE a score of 0.06033 (93rd percentile). For CVE-2026-120382, a raw-HTML link scan of Synology's advisories and press release found no exploit links, and none of the sources we opened mentions public exploit code. For CVE-2026-123007, Rapid7 has published proof-of-concept code. Rapid7 demonstrated it against a Docker image running NGINX 1.31.8 with HTTP/2 and TLS enabled, and Cloudflare reported on November 19 that Rapid7 describes it as suitable only for demonstrating the attack against a freshly started local container. Cloudflare also reported no exploitation in the wild as of November 19. No source we opened has tested that code against DSM, and we have not opened or run it.
Affected Product Versions
From Synology's two advisories, revision 2 of November 20, 2026. "OnGoing" is Synology's wording for a fix that is not yet available.
| Product | SA-26:21, CVE-2026-120382 (OAuth API) | SA-26:20, CVE-2026-123007 (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 (upgrading to 7.3.2-86009-6 or above is recommended) | OnGoing (upgrading to 7.3.2-86009-6 or above is recommended) |
| DSM 7.2.1 | OnGoing (upgrading to 7.3.2-86009-6 or above is recommended) | OnGoing (upgrading to 7.3.2-86009-6 or above is 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 |
When the fixed builds appeared. Synology's first version of SA-26:21, captured by the Internet Archive at 17:15 EST on November 19, listed both fixes as "scheduled for release by 2026-11-20." Synology's download archive shows the DSM 7.3.2-86009-6 files dated between 22:29 and 22:40 EST on November 19, and the DSM 7.4.1-90080-2 files between 00:22 and 00:34 EST on November 20. At 12:19 EST on November 20, and again at 15:42 EST and 15:44 EST on November 21, Synology's DSM release notes did not list either build; the newest entries were 7.4.1-90080 Update 1 (October 28) and 7.3.2-86009 Update 5 (October 12). Synology's notes for those earlier updates warn that a device may not be offered an update right away because rollout varies by region, and point to the archive for a manual update.
Timeline (EST)
- November 18, 2026, 10:00: the public disclosure time in the CVE-2026-123007 record; F5 and the nginx project release fixed NGINX versions the same day.
- November 19, 02:47: Synology publishes SA-26:20 and SA-26:21, with the DSM 7.4 and 7.3 fixes "scheduled for release by 2026-11-20."
- November 19, 22:29 to November 20, 00:34: the DSM 7.3.2-86009-6 and 7.4.1-90080-2 files are posted to Synology's download archive.
- November 20, 03:25: Synology revises both advisories ("Update fix status for DSM 7.3 and DSM 7.4") and issues a press release saying no exploitation has been observed.
- November 20, 12:16 and 12:18: no CVE.org or NVD record for CVE-2026-120382 when we checked.
- November 21, 15:41 to 15:49: we re-checked Synology's advisories and press release (still revision 2, text unchanged), the download archive and DSM release notes (still no further fixed builds, and the notes still do not list 7.4.1-90080-2 or 7.3.2-86009-6), CVE.org and NVD (still no record for CVE-2026-120382), and CISA's KEV catalog (catalogVersion 2026.11.20, 1,790 entries, neither CVE listed). We found no report of exploitation. The Internet Archive still serves the first version of SA-26:21 from a November 19, 17:15 EST capture of the en-us advisory; the earlier en-global capture at 12:36 EST that day was no longer served.
How to Find Your Exposure
These steps are Rescana guidance, not Synology's.
- List every Synology device you own and its exact build, including DSM, BeeStation OS, DSM Enterprise and APM systems, branch-office units and devices bought by individual teams. Anything on DSM 7.4 below 7.4.1-90080-2 or on DSM 7.3 below 7.3.2-86009-6 is in scope for both flaws, and every DSM 7.2.2, 7.2.1, 7.1 and BeeStation OS 1.5 device is in scope with no fix yet.
- Check whether OAuth Service is installed and running in Package Center on each device. Synology's mitigation is to deactivate it, so the package's state is the first thing to record.
- See what depends on OAuth Service before you turn it off. Synology's help for the package lists registered applications on its Application page and issued tokens on its Authorized Token page. Synology's own examples include Audio Station with Amazon Echo, third-party application sign-in and Dynamic Client Registration for AI Console. Note each one, because deactivating the package stops it.
- Check the HTTP/2 setting under Control Panel > Network > Connectivity. Synology's help describes HTTP/2 as an option you turn on with the Enable HTTP/2 box, so a ticked box means the device is in scope for CVE-2026-123007 until it is updated.
- Find out who can reach the DSM web interface. Synology's sign-in guide uses port 5000 for DSM, and Synology's port list gives 5001 as the default HTTPS port; also check the HTTP and HTTPS ports you configured, any router port forwarding, reverse proxies and other remote access paths. Synology does not say which remote access paths reach the OAuth API, so treat every one as exposure until Synology says otherwise.
- Ask suppliers the questions in the TPRM section below. Many Synology devices that hold your data are not yours.
Workaround and Mitigation
Synology's fix: upgrade. For DSM 7.4, "Upgrade to 7.4.1-90080-2 or above." For DSM 7.3, "Upgrade to 7.3.2-86009-6 or above." For DSM 7.2.2 and 7.2.1, "OnGoing (Upgrading to 7.3.2-86009-6 or above is recommended)." Synology "recommends that users install the updates as soon as possible."
Synology's mitigation for CVE-2026-120382 (SA-26:21): "Deactivate the OAuth Service package."
Synology's mitigation for CVE-2026-123007 (SA-26:20): "Disable HTTP/2 under Control Panel > Network > Connectivity."
Synology on these mitigations: its press release calls them "temporary mitigations" for "users who cannot update right away."
Additional steps (Rescana guidance, not Synology's).
- Update DSM 7.4 and 7.3 devices now. If a device does not offer the update, install the matching file from Synology's download archive, which Synology's own release notes point to for manual updates.
- Apply both mitigations together on anything you cannot update today. Deactivating OAuth Service addresses only CVE-2026-120382, and disabling HTTP/2 addresses only CVE-2026-123007.
- On DSM 7.2.2 and 7.2.1, plan the move to 7.3.2-86009-6 that Synology recommends, after checking that the model and your packages support DSM 7.3. Keep both mitigations in place until the move is done.
- On DSM 7.1 and BeeStation OS 1.5, apply the mitigations today and track SA-26:21 and SA-26:20 for a fixed release. There is no other vendor fix for these devices yet.
- Take the DSM web interface off the internet if it does not need to be there, and limit it to administrator networks or a VPN where it does. This is a stopgap and does not replace the update.
- Decide what to re-enable after updating. Turn OAuth Service and HTTP/2 back on only on devices that need them, and only once the device runs a fixed build.
- Keep a recent copy of important data off the device, so that a device whose files were altered can be restored from a known-good state.
- If you find changes you cannot explain, treat the device as potentially compromised. Preserve its logs, rotate the passwords and tokens stored on it, and rebuild from a known-good state.
Indicators of Compromise
Synology, CISA and NVD publish no indicators of compromise, network signatures or malware names for CVE-2026-120382 or for CVE-2026-123007 in Synology products, and none of them reports exploitation or names a threat actor. We list none and invent none.
Signals worth checking in the meantime (Rescana guidance): entries in the OAuth Service log, or applications and tokens on its Application and Authorized Token pages, that nobody can account for; files created or changed outside normal use, especially system or configuration files; new user accounts, scheduled tasks or packages; and repeated web service crashes or restarts, which is the typical result F5 describes for CVE-2026-123007. These are generic signs of misuse, not specific to these flaws. We will update this advisory if Synology or CISA publish indicators.
Third-Party Risk (TPRM) Angle
Synology NAS devices are common at the smaller suppliers that hold your documents: accountants, law firms, agencies, engineering and design firms, and the managed service providers that look after them. They are also widely used as backup targets, so a supplier's NAS may hold copies of systems and files that came from you. A flaw that lets an unauthenticated attacker read or write arbitrary files on such a device bears directly on the confidentiality and integrity of that data, and the supplier's passwords and multi-factor authentication do not help if the web interface is reachable (Rescana's reading).
The suppliers to ask first (Rescana guidance):
- Suppliers that store your files or deliverables on their own file servers.
- Managed service and backup providers that run Synology devices for themselves or for clients.
- Any supplier that gives your staff access to a Synology portal for file exchange.
Send these five questions (Rescana guidance):
- Do you run Synology DSM, BeeStation OS or DSM Enterprise devices that store our data or our backups, and which build is each device on?
- For DSM 7.4 and 7.3 devices, on what date did you update to 7.4.1-90080-2 or 7.3.2-86009-6? For devices without a fix, on what date did you deactivate OAuth Service and disable HTTP/2?
- Can the DSM web interface of those devices be reached from the internet, and through which paths?
- Have you reviewed the OAuth Service log, registered applications and recent file changes on those devices, back to what date, and what did you find?
- Do any of those devices run end-of-life DSM versions, and what is your plan for them?
Ask for evidence, not reassurance: the build each device reports, the date of each change, the review period and the result. Synology does not report exploitation, but the OAuth flaw needs no login and several branches have no fix yet, so set a follow-up for each supplier with an unpatched device.
We will update this advisory if Synology revises SA-26:21 or SA-26:20, ships fixes for the remaining branches, reports exploitation, or if a CVE record is published for CVE-2026-120382 or CISA adds either CVE to its catalog.
Need help working out which suppliers keep your data on Synology devices? Our team can help you prioritize them and track their answers. Talk to an expert
Sources
- Synology: Synology-SA-26:21 DSM, BeeStation OS: published November 19, 2026, 02:47 EST; last updated November 20, 2026, 03:25 EST; checked 12:15 EST and again 12:18 EST, November 20, 2026, and again 15:41 EST and 15:44 EST, November 21, 2026.
- Synology: Synology-SA-26:20 NGINX2Root: published November 19, 2026, 02:47 EST; last updated November 20, 2026, 03:25 EST; checked 12:15 EST and again 12:18 EST, November 20, 2026, and again 15:41 EST and 15:44 EST, November 21, 2026.
- Synology: Synology Releases Critical Security Updates: press release, November 20, 2026; checked 12:16 EST and again 12:18 EST, November 20, 2026, and again 15:41 EST and 15:44 EST, November 21, 2026.
- Internet Archive: Synology-SA-26:21 as captured November 19, 2026, 17:15 EST: first version (en-us), last updated 02:50 EST November 19, with the DSM 7.4 and 7.3 fixes still "scheduled for release by 2026-11-20"; checked 15:49 EST, November 21, 2026. The earlier en-global capture at 12:36 EST on November 19 was no longer served by the Archive when we re-checked.
- Synology: download archive for DSM, with the 7.4.1-90080-2 and 7.3.2-86009-6 folders: checked 12:19 EST, November 20, 2026, and again 15:42 EST and 15:48 EST, November 21, 2026.
- Synology: DSM release notes and OAuth Service release notes: checked 12:19 to 12:20 EST, November 20, 2026, and again 15:42 EST and 15:48 EST, November 21, 2026.
- Synology Knowledge Center: OAuth Service and Connectivity: checked 12:20 EST, November 20, 2026, and again 15:43 EST and 15:50 EST, November 21, 2026.
- Synology Knowledge Center: Signing in to DSM and What network ports are used by services on my Synology system?: default DSM ports 5000 (HTTP) and 5001 (HTTPS); checked 15:50 EST, November 21, 2026.
- CVE.org API: CVE-2026-123007: published November 18, 2026, F5 as CNA, updated November 20, 2026; checked 12:18 EST, November 20, 2026, and again 15:41 EST and 15:44 EST, November 21, 2026. The same API returned no record for CVE-2026-120382 at 12:16 and 12:18 EST on November 20, and again at 15:41 EST and 15:44 EST on November 21.
- NVD API: CVE-2026-123007 and query for CVE-2026-120382: status Modified with F5's scores, last modified November 20, 2026, and no results for CVE-2026-120382; checked 12:18 EST, November 20, 2026, and again 15:41 EST and 15:44 EST, November 21, 2026.
- CISA: KEV catalog JSON feed: catalogVersion 2026.11.20, released November 20, 2026, 12:48 EST, 1,790 entries; checked 15:41 EST and 15:44 EST, November 21, 2026 (catalogVersion 2026.11.18, 1,786 entries, was checked 12:18 EST, November 20, 2026).
- FIRST: EPSS API query for both CVEs: checked 12:18 EST, November 20, 2026, and again 15:42 EST and 15:48 EST, November 21, 2026.
- Rapid7: CVE-2026-123007 analysis and Cloudflare: nginx2root: checked 12:20 EST, November 20, 2026, and again 15:43 EST and 15:48 EST, November 21, 2026.



