CVE-2025-64421: coollabsio coolify · Incorrect Authorization
Affects coollabsio coolifySource CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 5 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| coollabsiocoolify | Affected
| Fixed in– |
GitHubcoollabsio/coolifypkg:github/coollabsio/coolifyOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
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.
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.