CVE-2025-64421: CWE-863: Incorrect Authorization in coollabsio coolify
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. In Coolify versions up to and including v4.0.0-beta.434, a low privileged user (member) can invite a high privileged user. At first, the application will throw an error, but if the attacker clicks the invite button a second time, it actually works. This way, a low privileged user can invite themselves as an administrator to the Coolify instance. After the high privileged user is invited, the attacker can initiate a password reset and log in with the new admin. As of time of publication, it is unclear if a patch is available.
AI Analysis
Technical Summary
CVE-2025-64421 is an authorization bypass vulnerability classified under CWE-863 affecting Coolify, an open-source and self-hostable tool designed for managing servers, applications, and databases. The vulnerability exists in Coolify versions up to and including 4.0.0-beta.434. It allows a low privileged user, specifically a member role, to escalate privileges by exploiting a flaw in the user invitation mechanism. When a low privileged user attempts to invite a high privileged user, the application initially returns an error, preventing the action. However, if the attacker clicks the invite button a second time, the system erroneously processes the invitation, effectively granting the attacker administrative privileges. Once the attacker has invited themselves as an administrator, they can initiate a password reset for the new admin account and gain full administrative access to the Coolify instance. This vulnerability is remotely exploitable without requiring user interaction beyond the repeated invite action and does not require prior authentication beyond low privilege membership. The CVSS 4.0 base score is 8.7 (high severity), reflecting the network attack vector, low attack complexity, no privileges required, and no user interaction needed. The impact on confidentiality, integrity, and availability is high, as an attacker can fully control the affected system. As of the publication date, no patch or fix has been confirmed, and no known exploits have been reported in the wild. This vulnerability poses a critical risk to organizations relying on Coolify for infrastructure management, potentially leading to unauthorized access, data compromise, and operational disruption.
Potential Impact
For European organizations, the impact of CVE-2025-64421 is significant due to the potential for complete administrative takeover of Coolify instances. Organizations using Coolify to manage servers, applications, or databases could face unauthorized access to sensitive data, disruption of services, and potential lateral movement within their networks. The ability for a low privileged user to escalate privileges without detection increases the risk of insider threats and external attackers exploiting compromised accounts. This could lead to data breaches, service outages, and loss of control over critical infrastructure components. Given the open-source nature of Coolify, many small to medium enterprises and development teams across Europe might deploy it, increasing the attack surface. The lack of a confirmed patch means organizations must rely on compensating controls, increasing operational overhead and risk. Regulatory compliance frameworks in Europe, such as GDPR, could be impacted if personal data is exposed due to this vulnerability, leading to legal and financial consequences.
Mitigation Recommendations
1. Immediately audit all Coolify instances to identify affected versions (<= 4.0.0-beta.434) and restrict membership roles to trusted users only. 2. Disable or restrict the invitation functionality for low privileged users until a patch is available. 3. Implement strict monitoring and alerting on invitation-related activities, especially repeated invite attempts by low privileged users. 4. Enforce multi-factor authentication (MFA) on all administrative accounts to reduce the risk of account takeover. 5. Isolate Coolify instances from public networks where possible, limiting access to trusted internal networks or VPNs. 6. Regularly review and rotate credentials associated with Coolify admin accounts. 7. Engage with the Coolify community or vendor to track patch releases and apply updates promptly once available. 8. Consider deploying web application firewalls (WAF) with custom rules to detect and block suspicious invitation requests. 9. Conduct internal penetration testing focused on privilege escalation vectors within Coolify to identify any additional weaknesses. 10. Prepare incident response plans specifically addressing potential Coolify compromise scenarios.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland, Denmark, Belgium, Italy, Spain
CVE-2025-64421: CWE-863: Incorrect Authorization in coollabsio coolify
Description
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. In Coolify versions up to and including v4.0.0-beta.434, a low privileged user (member) can invite a high privileged user. At first, the application will throw an error, but if the attacker clicks the invite button a second time, it actually works. This way, a low privileged user can invite themselves as an administrator to the Coolify instance. After the high privileged user is invited, the attacker can initiate a password reset and log in with the new admin. As of time of publication, it is unclear if a patch is available.
AI-Powered Analysis
Technical Analysis
CVE-2025-64421 is an authorization bypass vulnerability classified under CWE-863 affecting Coolify, an open-source and self-hostable tool designed for managing servers, applications, and databases. The vulnerability exists in Coolify versions up to and including 4.0.0-beta.434. It allows a low privileged user, specifically a member role, to escalate privileges by exploiting a flaw in the user invitation mechanism. When a low privileged user attempts to invite a high privileged user, the application initially returns an error, preventing the action. However, if the attacker clicks the invite button a second time, the system erroneously processes the invitation, effectively granting the attacker administrative privileges. Once the attacker has invited themselves as an administrator, they can initiate a password reset for the new admin account and gain full administrative access to the Coolify instance. This vulnerability is remotely exploitable without requiring user interaction beyond the repeated invite action and does not require prior authentication beyond low privilege membership. The CVSS 4.0 base score is 8.7 (high severity), reflecting the network attack vector, low attack complexity, no privileges required, and no user interaction needed. The impact on confidentiality, integrity, and availability is high, as an attacker can fully control the affected system. As of the publication date, no patch or fix has been confirmed, and no known exploits have been reported in the wild. This vulnerability poses a critical risk to organizations relying on Coolify for infrastructure management, potentially leading to unauthorized access, data compromise, and operational disruption.
Potential Impact
For European organizations, the impact of CVE-2025-64421 is significant due to the potential for complete administrative takeover of Coolify instances. Organizations using Coolify to manage servers, applications, or databases could face unauthorized access to sensitive data, disruption of services, and potential lateral movement within their networks. The ability for a low privileged user to escalate privileges without detection increases the risk of insider threats and external attackers exploiting compromised accounts. This could lead to data breaches, service outages, and loss of control over critical infrastructure components. Given the open-source nature of Coolify, many small to medium enterprises and development teams across Europe might deploy it, increasing the attack surface. The lack of a confirmed patch means organizations must rely on compensating controls, increasing operational overhead and risk. Regulatory compliance frameworks in Europe, such as GDPR, could be impacted if personal data is exposed due to this vulnerability, leading to legal and financial consequences.
Mitigation Recommendations
1. Immediately audit all Coolify instances to identify affected versions (<= 4.0.0-beta.434) and restrict membership roles to trusted users only. 2. Disable or restrict the invitation functionality for low privileged users until a patch is available. 3. Implement strict monitoring and alerting on invitation-related activities, especially repeated invite attempts by low privileged users. 4. Enforce multi-factor authentication (MFA) on all administrative accounts to reduce the risk of account takeover. 5. Isolate Coolify instances from public networks where possible, limiting access to trusted internal networks or VPNs. 6. Regularly review and rotate credentials associated with Coolify admin accounts. 7. Engage with the Coolify community or vendor to track patch releases and apply updates promptly once available. 8. Consider deploying web application firewalls (WAF) with custom rules to detect and block suspicious invitation requests. 9. Conduct internal penetration testing focused on privilege escalation vectors within Coolify to identify any additional weaknesses. 10. Prepare incident response plans specifically addressing potential Coolify compromise scenarios.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-11-03T22:12:51.364Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 695c16933839e441758db0b0
Added to database: 1/5/2026, 7:52:51 PM
Last enriched: 1/5/2026, 8:07:13 PM
Last updated: 1/8/2026, 5:07:52 AM
Views: 32
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.