Synology Advises OAuth Service Deactivation Pending DSM Security Fixes

P1 — VALIDATE AND UPDATECritical · 9.8 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Assess DSM and BeeStation exposure, deactivate the OAuth Service package as directed, and validate the availability of the appropriate supported fix.

Confirm Scope And Apply The Supported Remediation

What to do now: Record DSM or BeeStation versions, OAuth Service use, exposed interfaces and applications that depend on OAuth authentication. APM 2.0/1.2, DSM Enterprise 1.0 and SRM 1.3/1.2 are listed as not affected. Treat legacy CVE version boundaries separately from the product table’s Ongoing availability status. Deactivate the OAuth Service package as Synology directs. Once available, apply the listed supported DSM update; seek vendor guidance for BeeStation and other branches still under remediation. Test affected authentication workflows and alternative approved access, verify the running build after updating, and retain package, configuration and incident-review evidence.

Open the authoritative advisory

Last verified: 2026-11-19 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeSynology DSM OAuth API and BeeStation OS
AdvisorySynology-SA-26:21
CVECVE-2026-120382
Authoritative release date2026-11-19T07:47:20Z — Synology publication time, converted from UTC+8.
Authority revision dateSynology lists its last update separately as 2026-11-19T07:50:54Z; planned release availability is not a completed deployment.
Affected versionsThe product table marks BeeStation OS 1.5 and DSM 7.4, 7.3, 7.2.2, 7.2.1 and 7.1 as affected. The detailed CVE text lists 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; those boundaries do not establish update availability.
Fixed versionDSM 7.4.1-90080-2 and 7.3.2-86009-6 or later are scheduled for release by November 20, 2026. Other affected table rows remain Ongoing; obtain vendor confirmation for older branches.
CVSS base score9.8 (CVSS v3.1)
CVSS severityCritical
Exploitation statusThe cited authority does not confirm exploitation of these vulnerabilities in the wild.; no exploitation claim is inferred.

What Changed

Synology disclosed argument-delimiter handling in the DSM OAuth API that can permit arbitrary file reads or writes and denial of service. The product assessment is ongoing and separates planned DSM builds from the mitigation available now.

What To Validate Now

  1. Inventory. Record DSM or BeeStation versions, OAuth Service use, exposed interfaces and applications that depend on OAuth authentication.
  2. Establish applicability. APM 2.0/1.2, DSM Enterprise 1.0 and SRM 1.3/1.2 are listed as not affected. Treat legacy CVE version boundaries separately from the product table’s Ongoing availability status.
  3. Remediate. Deactivate the OAuth Service package as Synology directs. Once available, apply the listed supported DSM update; seek vendor guidance for BeeStation and other branches still under remediation.
  4. Validate. Test affected authentication workflows and alternative approved access, verify the running build after updating, and retain package, configuration and incident-review evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Deactivating OAuth Service can interrupt dependent authentication. Coordinate with application owners and preserve administrative recovery access. Do not infer arbitrary code execution or actual compromise from the CVSS score.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.