CVE-2025-22608

6.5 MEDIUM

📋 TL;DR

Coolify versions before 4.0.0-beta.361 have an authorization flaw where any authenticated user can revoke any team invitation by guessing predictable incremental IDs. This allows denial-of-service attacks against team management functionality. All Coolify instances running vulnerable versions 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: All Coolify deployments with team functionality enabled are vulnerable by default.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Malicious authenticated users could systematically revoke all team invitations, disrupting legitimate team onboarding and collaboration workflows.

🟠

Likely Case

Disgruntled or curious authenticated users revoke some team invitations, causing confusion and requiring manual re-invitation by administrators.

🟢

If Mitigated

With proper access controls and monitoring, impact is limited to minor administrative overhead for re-inviting users.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires authentication but is trivial once authenticated due to predictable IDs.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: 4.0.0-beta.361

Vendor Advisory: https://github.com/coollabsio/coolify/security/advisories/GHSA-qmxm-wvm9-wvxx

Restart Required: Yes

Instructions:

1. Backup your Coolify instance. 2. Update to version 4.0.0-beta.361 or later. 3. Restart the Coolify service. 4. Verify the update was successful.

🔧 Temporary Workarounds

Restrict user access

all

Limit user accounts to only trusted individuals until patching is complete.

Monitor invitation logs

all

Implement monitoring for invitation revocation events to detect abuse.

🧯 If You Can't Patch

  • Implement strict access controls and limit user accounts to essential personnel only.
  • Monitor system logs for suspicious invitation revocation patterns and investigate anomalies.

🔍 How to Verify

Check if Vulnerable:

Check Coolify version via web interface or configuration files. If version is below 4.0.0-beta.361, the system is vulnerable.

Check Version:

Check Coolify web interface dashboard or configuration files for version information.

Verify Fix Applied:

After updating, confirm version is 4.0.0-beta.361 or higher and test that authenticated users cannot revoke invitations they don't own.

📡 Detection & Monitoring

Log Indicators:

  • Multiple team invitation revocation events from single user accounts
  • Revocation of invitations not owned by the requesting user

Network Indicators:

  • HTTP POST requests to invitation revocation endpoints with predictable IDs

SIEM Query:

source="coolify" AND (event="invitation_revoked" OR path="/api/invitations/*/revoke") | stats count by user

🔗 References

📤 Share & Export