CVE-2025-22605

7.8 HIGH

📋 TL;DR

This vulnerability allows authenticated users in Coolify to execute arbitrary code on the Coolify container, potentially accessing sensitive data and private keys of other users/teams. Centrally hosted instances with open registration or multiple teams are especially at risk. The issue affects versions 4.0.0-beta.18 through 4.0.0-beta.252.

💻 Affected Systems

Products:
  • Coolify
Versions: 4.0.0-beta.18 through 4.0.0-beta.252
Operating Systems: All platforms running Coolify
Default Config Vulnerable: ⚠️ Yes
Notes: Centrally hosted instances with multiple teams or open registration are at highest risk. Single-user instances are less vulnerable but still affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of the Coolify container, allowing attackers to steal all user data, private keys, tokens, modify software behavior, and deploy malicious images to connected remote servers.

🟠

Likely Case

Authenticated attackers gaining unauthorized access to sensitive data of other users/teams and potentially compromising connected infrastructure.

🟢

If Mitigated

Limited impact if proper access controls and network segmentation are in place, though authenticated users could still exploit the vulnerability.

🌐 Internet-Facing: HIGH
🏢 Internal Only: HIGH

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires authenticated access to Coolify. The vulnerability involves command injection in remote server command execution.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 4.0.0-beta.253

Vendor Advisory: https://github.com/coollabsio/coolify/security/advisories/GHSA-9wqm-fg79-4748

Restart Required: No

Instructions:

1. Update Coolify to version 4.0.0-beta.253 or later. 2. Follow standard Coolify update procedures. 3. Verify the update was successful.

🔧 Temporary Workarounds

Restrict User Registration

all

Disable open registration and limit access to trusted users only

Implement Network Segmentation

all

Isolate Coolify container from sensitive infrastructure and other user environments

🧯 If You Can't Patch

  • Implement strict access controls and limit user permissions
  • Monitor for suspicious command execution patterns and user activity

🔍 How to Verify

Check if Vulnerable:

Check Coolify version. If between 4.0.0-beta.18 and 4.0.0-beta.252 inclusive, you are vulnerable.

Check Version:

Check Coolify web interface or deployment configuration for version information

Verify Fix Applied:

Verify Coolify version is 4.0.0-beta.253 or later and check that the patch commit (353245bb7de9680f238bae30443af1696bc977b0) is applied.

📡 Detection & Monitoring

Log Indicators:

  • Unusual command execution patterns
  • Unexpected user activity in remote server operations
  • Suspicious process creation in Coolify container

Network Indicators:

  • Unexpected outbound connections from Coolify container
  • Suspicious traffic to/from remote servers managed by Coolify

SIEM Query:

Search for command execution events in Coolify logs with unusual parameters or from unexpected users

🔗 References

📤 Share & Export