Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2025-34161 PoC — Coolify Git Repository Field Command Injection in Project Deployment Workflow

Source
Associated Vulnerability
Title: Coolify Git Repository Field Command Injection in Project Deployment Workflow (CVE-2025-34161)
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.
Description
Authenticated low-privileged RCE in Coolify via unsanitized shell commands in the Git Repository field.
Readme
| Field       | Value                          |
|-------------|--------------------------------|
| CVE ID      | CVE-2025-34161                 |
| Affected    | Coolify <= v4.0.0-beta.420.6   |
| Fixed in    | v4.0.0-beta.420.7              |
| Severity    | Critical                       |
| CVSS 4.0    | 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|
| CWE         | CWE-78 (OS Command Injection)  |


## 📝 Summary
Coolify versions prior to and including v4.0.0-beta.420.6 are vulnerable to a critical remote code execution (RCE) flaw in the project deployment workflow. The platform allows authenticated users, with low-level privileges, to inject arbitrary shell commands via the Git Repository URL 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.

## ⚡ Impact
- Remote Code Execution (RCE)
- Privilege escalation from low-level user to full host compromise
- Complete loss of confidentiality, integrity, and availability

## 🛠️ Steps to Reproduce
1. Login as a low-privileged user  
2. Create a new project
3. Select private GIT 
4. Insert a malicious payload in the `Git Repository URL` field (e.g. ``git@github.com:fake/repo.git; cat /etc/passwd #;``)  
5. Deploy the project → observe arbitrary command execution in the log 

## 🔗 References
- [CVE Record - CVE-2025-34161](https://cve.org/CVERecord?id=CVE-2025-34161)  

File Snapshot

Log in to view the POC file snapshot cached by Shenlong Bot

Log in to view
Remarks
    1. It is advised to access via the original source first.
    2. Local POC snapshots are reserved for subscribers — if the original source is unavailable, the local mirror is part of the paid plan.
    3. Mirroring, verifying, and maintaining this POC archive takes ongoing effort, so local snapshots are a paid feature. Your subscription keeps the archive online — thank you for the support. View subscription plans →