CVE-2025-34161

8.8 HIGH

📋 TL;DR

Coolify versions before v4.0.0-beta.420.7 contain a command injection vulnerability in the Git Repository field during project creation. Authenticated users with member privileges can execute arbitrary shell commands on the host system, potentially leading to complete server compromise. All deployments running vulnerable versions are affected.

💻 Affected Systems

Products:
  • Coolify
Versions: All versions prior to v4.0.0-beta.420.7
Operating Systems: All platforms running Coolify
Default Config Vulnerable: ⚠️ Yes
Notes: Requires authenticated user with member privileges; default installations are vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Full server compromise with attacker gaining root access, data exfiltration, lateral movement to other systems, and persistent backdoor installation.

🟠

Likely Case

Attacker gains shell access, installs cryptocurrency miners or malware, steals sensitive data, and uses the server for further attacks.

🟢

If Mitigated

Limited impact due to network segmentation, minimal user privileges, and monitoring catching suspicious activity early.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access but is straightforward with publicly available proof-of-concept.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: v4.0.0-beta.420.7

Vendor Advisory: https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.420.7

Restart Required: Yes

Instructions:

1. Backup your Coolify configuration and data. 2. Update to v4.0.0-beta.420.7 or later using the official upgrade instructions. 3. Restart the Coolify service. 4. Verify the update was successful.

🔧 Temporary Workarounds

Restrict User Privileges

all

Temporarily remove member privileges from untrusted users or restrict project creation capabilities.

Input Validation Filter

all

Implement WAF or proxy rules to block command injection patterns in Git repository fields.

🧯 If You Can't Patch

  • Isolate the Coolify server from critical networks and implement strict network segmentation.
  • Implement comprehensive monitoring and alerting for suspicious shell commands and process creation.

🔍 How to Verify

Check if Vulnerable:

Check your Coolify version in the web interface admin panel or via the CLI with 'coolify --version'.

Check Version:

coolify --version

Verify Fix Applied:

Confirm version is v4.0.0-beta.420.7 or later and test that command injection attempts in Git repository field are properly sanitized.

📡 Detection & Monitoring

Log Indicators:

  • Unusual shell commands in system logs
  • Suspicious process creation from Coolify user
  • Failed authentication attempts followed by successful member login

Network Indicators:

  • Outbound connections to suspicious IPs from Coolify server
  • Unexpected SSH or reverse shell traffic

SIEM Query:

source="coolify" AND (command="*;*" OR command="*|*" OR command="*`*" OR command="*$(*")

🔗 References

📤 Share & Export