# CVE-2025-34161: Coolify Git Repository Field Command Injection in Project Deployment Workflow

> Authenticated low-privilege users can execute arbitrary shell commands on the host via the Git Repository field, leading to full server compromise.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA: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:** 27 Aug 2025
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-xp99-74mm-rpv2

## What is CVE-2025-34161?

CVE-2025-34161 is a critical command injection vulnerability in coolLabs Technologies Coolify, published on 27 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Coolify versions prior to v4.0.0-beta.420.7 are vulnerable to a remote code execution vulnerability in the project deployment workflow. The platform allows authenticated users, with low-level member privileges, to inject arbitrary shell commands via the Git Repository field during project creation. By submitting a crafted repository string containing command injection syntax, an attacker can execute arbitrary commands on the underlying host system, resulting in full server compromise.

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

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

It affects 1 product.


Products: Coollabs Coolify.

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

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

## Is CVE-2025-34161 being exploited?

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

Public exploit code:

- Authenticated low-privileged RCE in Coolify via unsanitized shell commands in the Git Repository field. (github_poc): https://github.com/Eyodav/CVE-2025-34161

## Other vulnerabilities in coolLabs Technologies 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-34161 and fix it if it is affected.

What it is: CVE-2025-34161 is a critical command injection vulnerability in coolLabs Technologies Coolify, published on 27 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-34161 in the wild and no public exploit code.

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

## Sources

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

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