Skip to main content
VulnerabilityPublished

CVE-2025-59955: coollabsio coolify · Insertion of Sensitive Information Into Sent Data

Affects coollabsio coolifySource CVE Database V5

0

Public exploit available · CVSS 5.7 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
5.7Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  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), CVSS vector, 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.428
Fixed in–
GitHubcoollabsio/coolifypkg:github/coollabsio/coolifyOther threatsAffected
  • =4.0.0-beta.420.8
  • =4.0.0-beta.428
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Given the absence of patches, European organizations should implement the following specific mitigations: 1) Restrict team membership strictly to trusted personnel and regularly audit team memberships to minimize exposure. 2) Monitor API access logs for unusual or excessive requests to the affected endpoints that could indicate exploitation attempts. 3) Implement additional verification steps for email change requests outside of relying solely on the email_change_code, such as multi-factor authentication or manual approval workflows. 4) Isolate Coolify instances within segmented network zones with strict access controls to limit lateral movement if an account is compromised. 5) Educate users about the risks of unauthorized email changes and encourage immediate reporting of suspicious account activity. 6) Consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block suspicious API calls targeting the vulnerable endpoints. 7) Engage with the Coolify community or vendor to track the release of patches and plan prompt updates once available. 8) As a temporary measure, disable or limit API access to the affected endpoints if feasible without disrupting operations. These targeted actions go beyond generic advice and focus on reducing the attack surface and detecting exploitation attempts in the absence of an official fix.

Description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Coolify versions prior to and including v4.0.0-beta.420.8 have an information disclosure vulnerability in the `/api/v1/teams/{team_id}/members` and `/api/v1/teams/current/members` API endpoints allows authenticated team members to access a highly sensitive `email_change_code` from other users on the same team. This code is intended for a single-use email change verification and should be kept secret. Its exposure could enable a malicious actor to perform an unauthorized email address change on behalf of the victim. As of time of publication, no known patched versions exist.

References

Community reviews

Loading reviews…