# CVE-2025-14713: Information disclosure in C2 Identity Edge Server

> Remote attackers can obtain user credentials from the Synology C2 Identity Edge Server due to an exposed dangerous method.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-jmjf-jwvm-x7jx

## What is CVE-2025-14713?

CVE-2025-14713 is a high-severity vulnerability in Synology C2 Identity Edge Server, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Exposed Dangerous Method or Function vulnerability in Synology C2 Identity Edge Server package in DSM before 1.76.0-0307 allows remote attackers to obtain user credentials from the edge server.

Weakness: CWE-749 (Exposed Dangerous Method or Function)

## Which versions are affected by CVE-2025-14713?

It affects 1 product.


Products: Synology C2 Identity Edge Server.

## How do I fix CVE-2025-14713?

No fix has been published for CVE-2025-14713 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-14713 being exploited?

There is no known exploitation of CVE-2025-14713 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14713 and fix it if it is affected.

What it is: CVE-2025-14713 is a high-severity vulnerability in Synology C2 Identity Edge Server, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14713 in the wild and no public exploit code.

Affected product: Synology C2 Identity Edge Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-14713/ (Markdown: https://insights.sbomify.com/CVE-2025-14713/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-14713
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-14713
- OSV: https://osv.dev/vulnerability/CVE-2025-14713

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-14713/
Summaries are generated and may contain mistakes; the official description above is the record.