Synology C2 Identity Edge Server: CVE-2025-14713, fixed since December 2025, two CVSS scores
On November 13, 2026, the Zero Day Initiative published the Pwn2Own finding ZDI-26-1009. In the C2 Identity Edge Server package on a Synology DS925+, an unauthenticated caller can reach a function that hands out stored credentials. The identifier is CVE-2025-14713. This is not a fresh flaw: the fix has existed since December 2025. Synology released the update in advisory Synology-SA-25:18 (page header December 16, 2025, the revision table says December 15, 2025) and added the details on May 27, 2026; the CVE record carries the same date. What is new is the ZDI advisory of November 13, 2026. According to its timeline the report reached the vendor on November 18, 2025, and the coordinated release followed almost a year later.
What is affected and what to do
The advisory lists C2 Identity Edge Server for DSM 7.1, 7.2.1, 7.2.2 and 7.3, fixed from version 1.76.0-0307. Under mitigation Synology writes only "None", so no workaround short of the update is offered (verified, advisory read on November 15, 2026). The advisory's product table rates the packages "Critical" while its detail section rates the flaw "Important"; the advisory gives no explanation for that.
The check per device:
- Open Package Center, see whether C2 Identity Edge Server is installed, and read its version.
- If it is below 1.76.0-0307, install the update.
- Uninstall the package if nobody uses it any more. An unused package with a listening service only adds attack surface.
- If the package was reachable from a network you don't control, treat the credentials stored through it as leaked and change them (derived, no vendor recommendation).
6.5 or 7.5
ZDI rates the flaw 6.5 with vector AV:A, meaning reachable only from the same network segment. Synology and the NVD entry say 7.5 with AV:N, meaning over the network. Every other part of the vector is identical: no privileges, no user interaction, high confidentiality impact, no integrity or availability impact (verified, both sources fetched on November 15, 2026; the NVD page blocks bots, so we read the CVE record through the CVE JSON API). The difference lies only in who can reach the service. Synology and the NVD text speak of "remote attackers", while ZDI lists the flaw as network-adjacent. None of the sources explains how the two parties arrived at their rating; whether to read the values as a contradiction or as two assumptions about reachability is our interpretation.
For operations this means the lower score is no all-clear. Which value fits depends on who can reach the package. A scanner that reads the vendor's CVE record will probably report 7.5, a ticket based on ZDI says 6.5 (derived). Both tickets have the same fix.
One more data point helps with triage. In the CVE record the CISA coordinator records "Exploitation: none" and "Automatable: yes" (state of May 27, 2026, read on November 15, 2026). So no exploitation was known at that point, though an attack could run fully automated (reported). We did not check whether that has changed since the ZDI advisory.
Who should act now
Our assessment, not the vendor's: even on a pure office network the update should come soon, because the CVE record lists “Automatable: yes”; a maintenance window next week is defensible, sitting it out is not. Reachable from the internet at any point, it belongs on today's list, along with a review of the stored credentials. With the details public (CVE record since May 27, 2026, ZDI advisory since November 13, 2026), the effort to rebuild the attack drops (derived).
Open points: Why ZDI and Synology rate differently is unresolved. We checked no version on a device and ran no test of our own; this post reads the advisories. Whether the flaw has been exploited since November, we did not investigate.
Read next: Philips Hue Bridge: Pwn2Own flaws in the HomeKit service · Facebook and the Android gallery case in Italy · the Bambu Lab H3C on a company network · Stalwart 1.1.0 and the missing role rights
Further Reading
All pages fetched on November 15, 2026.
- ZDI, advisory ZDI-26-1009, primary source, verified (CVSS 6.5, AV:A, reported November 18, 2025)
- Synology, security advisory Synology-SA-25:18, vendor advisory, verified (fix 1.76.0-0307, CVSS 7.5, AV:N, mitigation None)
- NVD, CVE-2025-14713, primary source; bot-walled, content read through the CVE JSON API
- CVE JSON API, CVE-2025-14713, primary source, verified (published May 27, 2026, CISA entries Exploitation none, Automatable yes)
- FIRST, CVSS 3.1 specification, attack vector adjacent and network, primary source, verified
Am I affected if I only run DSM?+
Synology's advisory covers the C2 Identity Edge Server package and leaves the DSM operating system out. Without that package installed, you don't appear in its list of affected products. That reading is derived from the product table; the vendor doesn't state it.
Which CVSS score applies, 6.5 or 7.5?+
The sources do not explain the difference. ZDI rates the attack vector as adjacent (6.5), Synology and the CVE record as network (7.5). For prioritising, what counts is whether the package is reachable from networks you don't control; anyone adopting the vendor value works with 7.5.
Is there a workaround that avoids the update?+
Synology lists None under mitigation and names no workaround. Our own advice, not a vendor recommendation and untested by us: install the update, remove the package, or until then limit access to trusted networks with the firewall.
senn-tech