# CVE-2025-13593: Path traversal in ActiveProtect Agent

> Local attackers can write arbitrary files and cause denial of service during installation due to origin validation errors in Synology ActiveProtect Agent.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 2 Jun 2026
- **Also known as:** GHSA-r6c2-6c2c-g3cg

## What is CVE-2025-13593?

CVE-2025-13593 is a medium-severity path traversal vulnerability in Synology ActiveProtect Agent, published on 27 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Origin validation error vulnerability in Synology ActiveProtect Agent before 1.1.0-0439 allows local users to write arbitrary files with restricted content and conduct denial-of-service during installation.

Weakness: CWE-346 (Origin Validation Error)

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

It affects 1 product.


Products: Synology Activeprotect Agent.

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

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

## Is CVE-2025-13593 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13593 is a medium-severity path traversal vulnerability in Synology ActiveProtect Agent, published on 27 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-13593 in the wild and no public exploit code.

Affected product: Synology ActiveProtect Agent. 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-13593/ (Markdown: https://insights.sbomify.com/CVE-2025-13593/index.md)
```

## Sources

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

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