CVE-2026-120382: Critical Synology DSM OAuth Flaw Enables Arbitrary File Access

CVE-2026-120382: Critical Synology DSM OAuth Flaw Enables Arbitrary File Access

SOC Prime Team
SOC Prime Team linkedin icon Follow

Synology has disclosed a critical vulnerability affecting DiskStation Manager (DSM) and BeeStation OS that can allow unauthenticated remote attackers to read or write arbitrary files and trigger denial-of-service conditions. Tracked as CVE-2026-120382, the flaw resides in the OAuth API and carries a CVSS 3.1 score of 9.8, Critical.

The vulnerability is classified as CWE-88: Improper Neutralization of Argument Delimiters in a Command. According to Synology, the affected OAuth API fails to properly neutralize command argument delimiters, allowing attacker-controlled input to alter how a downstream command interprets its parameters. No authentication or user interaction is required.

The issue is particularly serious for organizations exposing Synology NAS management services to untrusted networks. Successful exploitation could expose confidential files stored on the NAS, allow attackers to modify or replace files, or disrupt device availability. Synology’s official advisory does not currently state that the vulnerability directly enables arbitrary command execution or remote code execution, so the confirmed impact should be limited to the vendor-documented file read/write and denial-of-service capabilities.

Contact Sales

The vulnerability affects multiple DSM generations as well as BeeStation OS 1.5. Synology recommends updating supported installations as soon as fixed builds become available and deactivating the OAuth Service package as an immediate workaround. As of November 20, 2026, the advisory remains marked Ongoing, with fixes for several affected product branches still in progress.

Organizations can use SOC Prime’s AI-Native Detection Intelligence Platform to operationalize emerging vulnerability intelligence and accelerate threat hunting and detection engineering across SIEM, EDR, XDR, and Data Lake environments.

Detect CVE-2026-120382 by correlating suspicious access to Synology authentication and OAuth functionality with unexpected file-system activity, unusual DSM service behavior, repeated service failures, and anomalous outbound connections from NAS devices.

CVE-2026-120382 analysis

CVE-2026-120382 affects Synology DiskStation Manager releases across several major branches. Synology’s detailed advisory lists vulnerable versions before DSM 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.

The current product matrix specifically marks the following supported products as affected:

ProductStatusFixed release / recommendation
BeeStation OS 1.5CriticalFix ongoing
DSM 7.4CriticalUpgrade to 7.4.1-90080-2 or later
DSM 7.3CriticalUpgrade to 7.3.2-86009-6 or later
DSM 7.2.2CriticalFix ongoing; upgrade to 7.3.2-86009-6+ recommended
DSM 7.2.1CriticalFix ongoing; upgrade to 7.3.2-86009-6+ recommended
DSM 7.1CriticalFix ongoing
APM 1.2 / 2.0Not affectedNo action for this CVE
DSM Enterprise 1.0Not affectedNo action for this CVE
SRM 1.2 / 1.3Not affectedNo action for this CVE

An important detail is that DSM 6.2 does not appear in Synology’s current affected-products table, but the technical version description explicitly identifies versions before DSM 6.2.4-25556-9 as vulnerable. Organizations maintaining older or end-of-life NAS systems should therefore verify the installed build instead of assuming that absence from the current support matrix means the system is safe.

The root cause involves improper handling of command argument delimiters inside the OAuth API. Argument injection differs from traditional OS command injection: rather than necessarily inserting an entirely new shell command, an attacker manipulates the arguments supplied to a legitimate backend command so it performs operations that were not intended by the application.

Synology has not publicly disclosed the vulnerable function, exact HTTP request format, affected OAuth endpoint, backend command, or the characters required to trigger the flaw. This is consistent with the company’s stated policy of limiting detailed vulnerability information until customers have access to fixes.

The CVSS vector is:

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

This means exploitation is network-accessible, has low attack complexity, requires no privileges, and does not require victim interaction. Successful attacks can have a high impact on confidentiality, integrity, and availability.

Arbitrary file read capability is especially significant on a NAS platform because these systems frequently store backups, business documents, credentials, configuration files, and other sensitive data. Depending on the permissions of the vulnerable service, attackers may be able to retrieve data that would normally require authenticated access.

Arbitrary file write capability introduces an additional integrity risk. An attacker may potentially overwrite existing data or create files at locations accessible to the vulnerable process. However, neither Synology nor the two supplied reports demonstrate a reliable path from this primitive to direct code execution, so CVE-2026-120382 should not currently be described as a confirmed RCE vulnerability.

Attackers could also use the vulnerability to disrupt availability. Synology explicitly lists denial-of-service as an impact, which could make the NAS or affected services temporarily unavailable and interfere with business operations, file sharing, backups, or applications depending on the device.

The OAuth Service is particularly important from an exposure perspective because OAuth functionality is intended to support authentication and authorization between applications and Synology services. Synology’s immediate workaround is therefore to deactivate the OAuth Service package, removing the vulnerable functionality from active use until a permanent update is installed.

The CVE-2026-120382 PoC status remains favorable to defenders at the time of writing. Neither Synology, CyberPress, nor GBHackers reports a publicly available proof-of-concept exploit, and no independently verified public exploit has been identified as of November 20, 2026.

There is likewise no confirmed evidence that the vulnerability is being exploited in the wild. Synology’s advisory does not describe active attacks, threat actors, exploitation telemetry, or a known campaign associated with the flaw. This is notably different from several other recent Synology vulnerabilities that have been linked to real-world ransomware or intrusion activity.

The absence of observed exploitation should not reduce patching priority. A remotely reachable, unauthenticated file read/write vulnerability with low attack complexity and a 9.8 CVSS score is an attractive target, particularly now that the existence and affected product range are public.

For CVE-2026-120382 detection, defenders should monitor Synology management interfaces for unusual unauthenticated requests, unexpected OAuth-related activity, abnormal HTTP request parameters, repeated request failures, and unexpected file-system operations occurring shortly after inbound network activity.

On organizations that centrally collect NAS telemetry, useful behavioral signals include unexpected creation or modification of configuration files, changes to application directories, suspicious access to sensitive files, unusual service restarts, and unexplained resource exhaustion or service availability problems.

Network telemetry can provide additional context. Security teams should investigate unusual connections to exposed Synology NAS interfaces from unfamiliar external addresses, particularly where the same source generates repeated requests immediately before unexpected file modifications or service instability.

Because the flaw is remotely exploitable without credentials, defenders should not restrict hunting to successful DSM logins. A malicious request may reach the vulnerable OAuth functionality without creating the authentication events normally associated with legitimate administrative activity.

Organizations should also audit internet exposure. NAS management interfaces generally should not be directly accessible from the public internet unless operational requirements demand it. VPN access, private management networks, IP allowlisting, and reverse-proxy controls can materially reduce the attack surface while permanent updates are being deployed.

Traditional CVE-2026-120382 IOCs are currently unavailable. Synology has not published malicious IP addresses, domains, payload hashes, request signatures, or attacker infrastructure associated with the vulnerability because no campaign has been publicly linked to exploitation.

This makes behavior-based detection and asset exposure management more valuable than static IOC matching. Security teams should identify vulnerable devices first, determine whether the OAuth Service is active, establish whether the NAS is reachable from untrusted networks, and then investigate anomalies that could indicate probing or exploitation.

The vulnerability was publicly disclosed on November 19, 2026, when Synology published advisory Synology-SA-26:21. The advisory was updated only minutes later and remains in Ongoing status. Synology has not disclosed the original vulnerability discovery date or publicly credited a specific researcher in the advisory.

The CyberPress and GBHackers reports also cover CVE-2026-123007, an unrelated NGINX HTTP/2 vulnerability affecting some of the same Synology platforms. Administrators should not confuse the two flaws: disabling OAuth addresses the immediate exposure for this vulnerability, while CVE-2026-123007 requires separate remediation such as disabling HTTP/2 or installing the corresponding fixed build.

Security teams looking for additional details for CVE-2026-120382 should monitor Synology-SA-26:21 because fix availability remains dynamic across DSM and BeeStation OS branches. The vendor advisory should take precedence over third-party vulnerability databases when determining whether a particular NAS build has received a supported fix.

CVE-2026-120382 Mitigation

The preferred remediation is to upgrade affected Synology systems to a fixed DSM version as soon as the appropriate package is available.

Synology identifies:

  • DSM 7.4: upgrade to 7.4.1-90080-2 or later.
  • DSM 7.3: upgrade to 7.3.2-86009-6 or later.
  • DSM 7.2.2 and 7.2.1: Synology recommends moving to 7.3.2-86009-6 or later.
  • DSM 7.1: remediation remains listed as ongoing.
  • BeeStation OS 1.5: remediation remains listed as ongoing.

As of the latest advisory revision available on November 20, the DSM 7.3 and 7.4 fixed builds are described as scheduled for release by November 20 rather than confirmed universally available across every device and region. Administrators should therefore verify availability through the Synology Update & Restore interface or Download Center rather than assuming the update has already reached their NAS.

If an update is not yet available, Synology’s official temporary workaround is straightforward:

Deactivate the OAuth Service package.

This mitigation should remain in place until the device has been updated to a version containing the fix.

Administrators should first determine whether legitimate applications rely on OAuth functionality. Disabling the package may interrupt integrations that use it for authorization, but the operational impact should be balanced against a remotely exploitable vulnerability with a 9.8 CVSS score.

Organizations should also restrict management interfaces from unnecessary internet exposure. Place NAS administration behind a VPN or dedicated management network and use firewall rules to limit connections to trusted administrators and systems.

Where possible, security teams should block direct inbound access to NAS management services from the internet. This does not replace the vendor patch because an attacker with access to the internal network could still target a vulnerable system, but it substantially reduces exposure to opportunistic scanning.

After applying the update, verify the installed DSM build rather than assuming an automatic-update notification confirms remediation. Synology notes that updates may become available at different times depending on region, model, and system configuration.

Devices running older DSM branches deserve additional attention. The technical advisory indicates that DSM versions before 6.2.4-25556-9 are affected, while modern remediation guidance centers primarily on supported 7.x releases. Organizations that cannot move an older appliance to a supported secure release should consider replacing, isolating, or removing that system from untrusted networks.

Security teams should also inspect systems that were publicly accessible before remediation. Review OAuth-related logs, administrative activity, file changes, service restarts, and unusual network events for evidence that exploitation attempts occurred before the update or workaround was applied.

Because arbitrary file writes are part of the confirmed impact, unexplained modification of configuration or application files should be treated more seriously than a normal failed authentication attempt. If suspicious file changes are identified, organizations should assess the NAS as potentially compromised rather than simply restoring the modified files.

Important data stored on NAS appliances should be protected by independent backups that attackers cannot modify through the same management plane. Maintaining offline, immutable, or separately authenticated backup copies can limit the operational impact of NAS compromise.

Detection content may not be available for every CVE. Check the SOC Prime Platform for current coverage. If relevant detections are not yet available, check again as new threat intelligence and detection content are continuously added.

FAQ

What is CVE-2026-120382 and how does it work?

CVE-2026-120382 is a critical argument-delimiter injection vulnerability in the OAuth API used by Synology DiskStation Manager. Improper neutralization of command arguments can allow an unauthenticated remote attacker to influence a backend command and gain the ability to read or write arbitrary files or cause denial of service. Synology classifies the weakness as CWE-88 and assigns it a CVSS 3.1 score of 9.8.

When was CVE-2026-120382 first discovered?

Synology has not publicly disclosed the original discovery date or named a researcher in the current advisory. The vulnerability became public on November 19, 2026, when Synology published Synology-SA-26:21. The advisory was last updated minutes after its initial publication and remains marked Ongoing while fixes for several affected branches are still being prepared.

What is the impact of CVE-2026-120382 on systems?

Successful exploitation can allow an unauthenticated remote attacker to read arbitrary files, write arbitrary files, and trigger denial-of-service conditions on affected Synology systems. This could expose sensitive NAS data, allow unauthorized modification of stored files, or disrupt services. Synology has not stated that the vulnerability directly provides arbitrary command execution or RCE.

Can CVE-2026-120382 still affect me in 2026?

Yes. Systems running affected DSM builds or BeeStation OS 1.5 remain exposed until the appropriate security update is installed or the OAuth Service is deactivated. The advisory includes affected DSM branches from 6.2 through 7.4, although current support and patch availability differ by release.

How can I protect myself from CVE-2026-120382?

Install the relevant Synology security update as soon as it becomes available. DSM 7.4 systems should move to 7.4.1-90080-2 or later, while DSM 7.3 systems should move to 7.3.2-86009-6 or later. If the update is not yet available, deactivate the OAuth Service package, restrict NAS administration to trusted networks, and avoid exposing management interfaces directly to the internet.

Join SOC Prime's Detection as Code platform to improve visibility into threats most relevant to your business. To help you get started and drive immediate value, book a meeting now with SOC Prime experts.

More CVEs Articles