CVE
Synology DiskStation Manager authentication bypass in SSO API
Affects Synology DSM before 7.2.2-72806-5 and 7.3.1-86003-1; DSM 7.2.1-69057 is not affected. Fixed in 7.2.2-72806-5 and 7.3.1-86003-1.
- Exploited
- No known exploitation
- Fix
- Fixed in 7.3.1-86003-1, 7.2.2-72806-5
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 7.3.1-86003-1, 7.2.2-72806-5.
Summary
Synology DiskStation Manager (DSM) has an authentication flaw in its SSO API. A remote attacker who knows the distinguished name (DN) can read or write arbitrary files and cause denial of service, and can reach the flaw over the network without logging in.
Original description
An incorrect implementation of authentication algorithm vulnerability in the SSO API 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 read or write arbitrary files and conduct denial-of-service attacks with prior knowledge of the distinguished name (DN).
Who should check
Teams running Synology DiskStation Manager (DSM) 7.2.2 or 7.3.x with the SSO API exposed, before the fixed builds.
“Synology DiskStation Manager (DSM) before 7.2.2-72806-5 and 7.3.1-86003-1”
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.1/10CVSS 8.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 7.3.1-86003-1, 7.2.2-72806-5.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2025-15716 (An incorrect implementation of authentication algorithm vulnerability in the SSO API in Synology DiskStation Manager (DSM) before…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2025-15716 (entry last updated 2026-11-18):
Affected:
- Synology DiskStation Manager (DSM): from 7.3.1, fixed in 7.3.1-86003-1; from 7.2.2, fixed in 7.2.2-72806-5
Fixed versions: 7.3.1-86003-1, 7.2.2-72806-5.
Conditions (all must be true for the bug to be hit):
- Affected DSM versions are those before 7.2.2-72806-5 and 7.3.1-86003-1; DSM 7.2.1-69057 is not affected. (source: https://www.synology.com/en-global/security/advisory/Synology_SA_25_14)
- Attacker needs prior knowledge of the distinguished name (DN). (source: https://www.synology.com/en-global/security/advisory/Synology_SA_25_14)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2025-15716 is not listed as of cve.now's last read.
This KEV status is for CVE-2025-15716 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.synology.com/en-global/security/advisory/Synology_SA_25_14
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2025-15716
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2025-15716"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Synology DiskStation Manager (DSM)
From 7.3.1 · fixed in 7.3.1-86003-1; From 7.2.2 · fixed in 7.2.2-72806-5
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | synology.com · en-global/security/advisory/Synology_SA_25_14 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2025-15716 |
| Record | NVD · CVE-2025-15716 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2025-15716
Is CVE-2025-15716 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The SSO API in DiskStation Manager uses an incorrect authentication algorithm. Per the record, this allows remote attackers to read or write arbitrary files and conduct denial-of-service attacks.Source: synology.com
Which versions are affected by CVE-2025-15716?
DiskStation Manager (DSM): from 7.3.1 before 7.3.1-86003-1; from 7.2.2 before 7.2.2-72806-5.Source: cve.now feed data
Am I affected, and how do I check?
DSM versions before 7.2.2-72806-5 and 7.3.1-86003-1 are affected, while DSM 7.2.1-69057 is not. Compare the installed DSM build against these versions. The record also notes that an attacker needs prior knowledge of the distinguished name (DN).Source: synology.com
How do I fix CVE-2025-15716?
Upgrade to DSM 7.2.2-72806-5 on the 7.2.2 branch or to DSM 7.3.1-86003-1 on the 7.3.1 branch.Source: synology.com