# CVE-2025-30407: Privilege escalation in Acronis Cyber Protect Cloud Agent

> Local attackers can escalate privileges via binary hijacking in the Acronis Cyber Protect Cloud Agent for Windows.

- **Severity:** Medium 6.3 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-27hm-58j3-pqh7

## What is CVE-2025-30407?

CVE-2025-30407 is a medium-severity vulnerability in Acronis Cyber Protect Cloud Agent, published on 26 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Local privilege escalation due to a binary hijacking vulnerability. The following products are affected: Acronis Cyber Protect Cloud Agent (Windows) before build 39713.

Weakness: CWE-426 (Untrusted Search Path)

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


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

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

## Is CVE-2025-30407 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30407 is a medium-severity vulnerability in Acronis Cyber Protect Cloud Agent, published on 26 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30407 in the wild and no public exploit code.

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

## Sources

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

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