# CVE-2025-22606: Coolify Command Injection Vulnerability in Project Name

> Attackers can execute arbitrary shell commands on the host server by injecting malicious characters into the project name field.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **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:** 24 Jan 2025
- **Updated:** 12 Feb 2025
- **Also known as:** GHSA-ccp8-v65g-m526

## What is CVE-2025-22606?

CVE-2025-22606 is a high-severity command injection vulnerability in coollabsio coolify, published on 24 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. In version 4.0.0-beta.358 and possibly earlier versions, when creating or updating a "project," it is possible to inject arbitrary shell commands by altering the project name. If a name includes unescaped characters, such as single quotes (`'`), it breaks out of the intended command structure, allowing attackers to execute arbitrary commands on the host system. This vulnerability allows attackers to execute arbitrary commands on the host server, which could result in full system compromise; create, modify, or delete sensitive system files; and escalate privileges depending on the permissions of the executed process. Attackers with access to project management features could exploit this flaw to gain unauthorized control over the host environment. Version 4.0.0-beta.359 fixes this issue.

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

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

It affects 1 product.


Products: Coollabs Coolify.

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

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

## Is CVE-2025-22606 being exploited?

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

## 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-66209](https://insights.sbomify.com/CVE-2025-66209/): Coolify Vulnerable to Authenticated Remote Code Execution via Command Injection in Database Backup (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)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22606 is a high-severity command injection vulnerability in coollabsio coolify, published on 24 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22606 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-22606/ (Markdown: https://insights.sbomify.com/CVE-2025-22606/index.md)
```

## Sources

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

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