Skip to main content
VulnerabilityPublished

CVE-2025-64420: coollabsio coolify · Insufficiently Protected Credentials

Affects coollabsio coolifySource CVE Database V5

0

Not known to be exploited · CVSS 10.0 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
coollabsiocoolifyAffected
  • <=4.0.0-beta.434
Fixed in–
GitHubcoollabsio/coolifypkg:github/coollabsio/coolifyOther threatsAffected
  • =4.0.0-beta.434
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 restrict access to Coolify instances to trusted administrators only, removing or limiting low privileged user accounts.
  2. Isolate Coolify deployments within segmented network zones to reduce exposure.
  3. Implement strict file system permissions to prevent unauthorized access to private keys and sensitive files.
  4. Monitor SSH logs and authentication attempts for unusual root login activity, enabling rapid detection of exploitation.
  5. Use multi-factor authentication (MFA) for all administrative access where possible to add an additional security layer.
  6. Consider temporarily disabling Coolify or migrating critical workloads until a patch is released.
  7. Regularly audit Coolify configurations and user privileges to ensure least privilege principles are enforced.
  8. Stay informed on vendor updates and apply patches promptly once available.
  9. Employ host-based intrusion detection systems (HIDS) to alert on unauthorized file access or privilege escalations.
  10. Educate users about the risks and signs of compromise related to this vulnerability.

Description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. In Coolify versions prior to and including v4.0.0-beta.434, low privileged users are able to see the private key of the root user on the Coolify instance. This allows them to ssh to the server and authenticate as root user, using the private key. As of time of publication, it is unclear if a patch is available.

References

Community reviews

Loading reviews…