CVE-2025-64422

4.3 MEDIUM

📋 TL;DR

Coolify's login endpoint has a rate limit bypass vulnerability that allows attackers to perform unlimited credential stuffing and brute-force attacks against user and admin accounts. This affects all Coolify instances running vulnerable versions, particularly those exposed to the internet. Attackers can exploit this to compromise accounts and gain unauthorized access.

💻 Affected Systems

Products:
  • Coolify
Versions: 4.0.0-beta.434 and later
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments with the vulnerable login endpoint are affected regardless of configuration.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers compromise admin accounts, gain full control of the Coolify instance, and potentially access managed servers, applications, and databases.

🟠

Likely Case

Attackers successfully brute-force user credentials, leading to unauthorized access to applications and data managed through Coolify.

🟢

If Mitigated

With proper network controls and monitoring, attacks are detected and blocked before successful account compromise.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploitation requires only rotating the X-Forwarded-For header, which is trivial to automate.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: https://github.com/coollabsio/coolify/security/advisories/GHSA-688j-rm43-5r8x

Restart Required: No

Instructions:

Monitor the vendor advisory for patch availability. No official patch exists at publication time.

🔧 Temporary Workarounds

Implement WAF Rate Limiting

all

Configure a web application firewall or reverse proxy to enforce rate limits on the /login endpoint, ignoring X-Forwarded-For headers.

Network Segmentation

all

Restrict access to Coolify's login endpoint to trusted IP ranges only.

🧯 If You Can't Patch

  • Implement strong password policies and multi-factor authentication for all accounts.
  • Monitor authentication logs for unusual login patterns and failed attempts.

🔍 How to Verify

Check if Vulnerable:

Test the /login endpoint by sending multiple requests with different X-Forwarded-For headers. If requests are not blocked after 5 attempts, the system is vulnerable.

Check Version:

Check Coolify's web interface or configuration files for version information. Typically displayed in the admin panel.

Verify Fix Applied:

Repeat the vulnerability test after applying controls. Successful rate limiting should block requests after 5 attempts regardless of X-Forwarded-For header changes.

📡 Detection & Monitoring

Log Indicators:

  • Multiple failed login attempts from the same IP with varying X-Forwarded-For headers
  • Unusual login patterns outside normal hours

Network Indicators:

  • High volume of POST requests to /login endpoint
  • Rapid X-Forwarded-For header rotation in requests

SIEM Query:

source="coolify" AND (url_path="/login" AND http_method="POST") | stats count by src_ip, x_forwarded_for

🔗 References

📤 Share & Export