# CVE-2025-66209: Coolify Vulnerable to Authenticated Remote Code Execution via Command Injection in Database Backup

> Authenticated users can execute arbitrary root commands via unsanitized database names in backup operations, requiring an upgrade to Coolify.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Dec 2025
- **Updated:** 17 Mar 2026
- **Also known as:** GHSA-vm5p-43qh-7pmq

## What is CVE-2025-66209?

CVE-2025-66209 is a critical command injection vulnerability in coollabsio coolify, published on 23 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to version 4.0.0-beta.451, an authenticated command injection vulnerability in the Database Backup functionality allows users with application/service management permissions to execute arbitrary commands as root on managed servers. Database names used in backup operations are passed directly to shell commands without sanitization, enabling full remote code execution. Version 4.0.0-beta.451 fixes the issue.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Coollabs Coolify.

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

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

## Is CVE-2025-66209 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66209 exists.

Public exploit code:

- Public security advisory for CVE-2025-66209, CVE-2025-66210, CVE-2025-66211, CVE-2025-66212, and CVE-2025-66213 (github_poc): https://github.com/0xrakan/coolify-cve-2025-66209-66213

## Other vulnerabilities in coollabsio coolify

- [CVE-2025-59157](https://insights.sbomify.com/CVE-2025-59157/): Coolify has Git Repository RCE (critical 10.0)
- [CVE-2025-64420](https://insights.sbomify.com/CVE-2025-64420/): Coolify members can see private key of root user (critical 10.0)
- [CVE-2025-22609](https://insights.sbomify.com/CVE-2025-22609/): Coolify Vulnerable to Private Key Hijacking / Remote Command Execution (RCE) (critical 10.0)
- [CVE-2025-22611](https://insights.sbomify.com/CVE-2025-22611/): Coolify vulnerable to Privilege Escalation resulting in Remote Command Execution (RCE) (critical 10.0)
- [CVE-2025-22612](https://insights.sbomify.com/CVE-2025-22612/): Coolify Vulnerable to Private Key Enumeration on Onboarding resulting in Remote Command Execution (RCE) (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66209 is a critical command injection vulnerability in coollabsio coolify, published on 23 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66209 exists.

Affected product: coollabsio coolify. 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-66209/ (Markdown: https://insights.sbomify.com/CVE-2025-66209/index.md)
```

## Sources

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

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