# CVE-2025-30028: Path traversal in Active Backup for Business

> Unauthorized remote attackers can read arbitrary files in Synology Active Backup for Business due to a path traversal vulnerability.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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-7vp3-7c6g-7rvm

## What is CVE-2025-30028?

CVE-2025-30028 is a high-severity path traversal vulnerability in Synology Active Backup for Business, published on 27 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Active Backup for Business allows unauthorized remote attackers to read arbitrary files.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Synology Active Backup for Business.

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

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

## Is CVE-2025-30028 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30028 is a high-severity path traversal vulnerability in Synology Active Backup for Business, 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-30028 in the wild and no public exploit code.

Affected product: Synology Active Backup for Business. 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-30028/ (Markdown: https://insights.sbomify.com/CVE-2025-30028/index.md)
```

## Sources

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

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