dbcve.org
Diskstation ManagerOperating system · Synology

CVE-2025-13392

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-27
Fix available
A fix is available. Upgrade to 7.2.2-72806-5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper check for unusual or exceptional conditions vulnerability in SSO in Synology DiskStation Manager (DSM) before 7.2.2-72806-5 and 7.3.1-86003-1 (7.2.1-69057 is not affected) allows remote attackers to bypass authentication with prior knowledge of the distinguished name (DN).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Synology DSM's SSO component contains an improper check for unusual or exceptional conditions that allows remote attackers with prior knowledge of a user's distinguished name (DN) to bypass authentication entirely. This is a critical authentication bypass vulnerability in the Single Sign-On implementation.

MitigationUpgrade DSM to version 7.2.2-72806-5 or 7.3.1-86003-1 or later. As compensating controls, restrict access to the management interface via network segmentation/VPN and enforce additional authentication factors until patching is complete.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Diskstation ManagerOperating system
Affected:>= 7.2.2, < 7.2.2-72806-5>= 7.3, <= 7.3.1-86003-1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check DSM major and minor version
    In DSM, go to Control Panel > System > System Information > Version, or run `cat /etc/VERSION` via SSH. Note the version number (e.g., 7.2.2, 7.3, 7.3.1).
    Affected if Version is 7.2.2 or higher but lower than 7.2.2-72806-5, OR version is 7.3.x up to and including 7.3.1-86003-1
  2. Check full build number
    In DSM System Information, locate the Build Number field (e.g., 72806-5). This is the complete version identifier after the minor version.
    Affected if Build number is lower than 72806-5 for DSM 7.2.2, or is 86003-1 or lower for DSM 7.3.1 (exact vulnerable builds: 7.2.2 through 7.2.2-72806-4, and 7.3 through 7.3.1-86003-1)
  3. Verify if SSO Server is configured
    In DSM, go to Control Panel > Domain & LDAP > SSO Server. Check if the SSO Server service is enabled.
    Affected if SSO Server is enabled and the DSM version/build falls into the affected ranges from steps 1-2
  4. Verify if SSO Client is configured
    In DSM, go to Control Panel > Domain & LDAP > SSO Client. Check if the SSO Client is enabled and connected to an external SSO Provider.
    Affected if SSO Client is enabled and the DSM version/build falls into the affected ranges from steps 1-2

A user is affected if their DSM version is 7.2.2 through 7.2.2-72806-4 or 7.3 through 7.3.1-86003-1, AND the SSO Server or SSO Client feature is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.2.2-72806-5 or later
Fixed in 7.2.2-72806-5
Interim mitigation

Upgrade DSM to version 7.2.2-72806-5 or 7.3.1-86003-1 or later. As compensating controls, restrict access to the management interface via network segmentation/VPN and enforce additional authentication factors until patching is complete.

Recommended fix High confidence

DSM 7.2.2-72806-5 (7.2.x branch) or DSM 7.3.1-86003-1 (7.3.x branch)

  1. Log in to Synology DiskStation Manager as an administrator
  2. Navigate to Control Panel > Update & Restore > DSM Update
  3. Click on 'Download Update' or 'Update Now' to check for available updates
  4. Select and install the appropriate update: For DSM 7.2.x, install version 7.2.2-72806-5 or later; For DSM 7.3.x, install version 7.3.1-86003-1 or later
  5. Wait for the update to complete and for the system to reboot
  6. Verify the update was successful by checking the DSM version under Control Panel > About > DSM
Caveat Standard DSM update - requires reboot and brief downtime; backup data before updating as a precaution

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Diskstation Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13392 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13392 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data