CVE-2025-22611

9.9 CRITICAL

📋 TL;DR

This vulnerability in Coolify allows any authenticated user to escalate privileges to any role, including owner, and remove all other team members. Attackers can then access the Terminal feature to execute remote commands. All Coolify instances running versions before 4.0.0-beta.361 are affected.

💻 Affected Systems

Products:
  • Coolify
Versions: All versions prior to 4.0.0-beta.361
Operating Systems: All platforms running Coolify
Default Config Vulnerable: ⚠️ Yes
Notes: Any Coolify instance with user authentication enabled is vulnerable. The vulnerability exists in the authorization logic, not in specific configurations.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of the Coolify instance with remote code execution, allowing attackers to control all managed servers, applications, and databases.

🟠

Likely Case

Privilege escalation leading to unauthorized access to sensitive systems and data, potentially enabling lateral movement to connected infrastructure.

🟢

If Mitigated

Limited impact if strong network segmentation and access controls prevent lateral movement from the compromised Coolify instance.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires authenticated access but is straightforward once authenticated. The advisory provides technical details that could facilitate exploitation.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 4.0.0-beta.361

Vendor Advisory: https://github.com/coollabsio/coolify/security/advisories/GHSA-9w72-9qww-qj6g

Restart Required: Yes

Instructions:

1. Backup your Coolify configuration and data. 2. Update Coolify to version 4.0.0-beta.361 or later using your deployment method (Docker, manual, etc.). 3. Restart the Coolify service. 4. Verify the update was successful.

🔧 Temporary Workarounds

Disable user authentication

all

Temporarily disable all user authentication to prevent exploitation, though this leaves the system completely open.

Network isolation

all

Restrict network access to Coolify to only trusted IP addresses while preparing for patching.

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate Coolify from production systems
  • Monitor all user activity and privilege changes in Coolify logs for suspicious behavior

🔍 How to Verify

Check if Vulnerable:

Check your Coolify version. If it's earlier than 4.0.0-beta.361, you are vulnerable.

Check Version:

Check the Coolify web interface dashboard or run: docker inspect coolify | grep VERSION

Verify Fix Applied:

After updating, verify the version is 4.0.0-beta.361 or later and test that authenticated users cannot escalate privileges or remove team members.

📡 Detection & Monitoring

Log Indicators:

  • Unexpected privilege escalation events
  • Team member removal events
  • Unauthorized access to Terminal feature

Network Indicators:

  • Unusual outbound connections from Coolify instance to managed servers

SIEM Query:

source="coolify" AND (event="privilege_escalation" OR event="member_removed" OR event="terminal_access")

🔗 References

📤 Share & Export