# CVE-2025-30415: Denial of service in Acronis Cyber Protect 17

> Attackers can cause a denial of service in Acronis Cyber Protect products by sending malformed input, requiring an upgrade to fixed builds.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jun 2025
- **Updated:** 17 Mar 2026
- **Also known as:** GHSA-5556-q3wj-f3qc

## What is CVE-2025-30415?

CVE-2025-30415 is a high-severity denial of service vulnerability in Acronis Cyber Protect 17, published on 4 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Denial of service due to improper handling of malformed input. The following products are affected: Acronis Cyber Protect Cloud Agent (Linux, macOS, Windows) before build 40077, Acronis Cyber Protect 17 (Linux, macOS, Windows) before build 41186.

Weakness: CWE-1286 (Improper Validation of Syntactic Correctness of Input)

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


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

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

## Is CVE-2025-30415 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30415 is a high-severity denial of service vulnerability in Acronis Cyber Protect 17, published on 4 Jun 2025. 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-30415 in the wild and no public exploit code.

Affected product: Acronis Cyber Protect 17. 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-30415/ (Markdown: https://insights.sbomify.com/CVE-2025-30415/index.md)
```

## Sources

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

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