# CVE-2025-59955: Coolify leaksensitive information `email_change_code` in `/api/v1/teams/{team_id | current}/members` API endpoint

> Authenticated team members can read sensitive email change codes from other users, potentially enabling unauthorized email address changes.

- **Severity:** Medium 5.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jan 2026
- **Updated:** 5 Jan 2026
- **Also known as:** GHSA-927g-56xp-6427

## What is CVE-2025-59955?

CVE-2025-59955 is a medium-severity vulnerability in coollabsio coolify, published on 5 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-214 (Invocation of Process Using Visible Sensitive Information), CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer), CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2025-59955?

It affects 1 product.


Products: Coollabs Coolify.

## How do I fix CVE-2025-59955?

No fix has been published for CVE-2025-59955 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59955 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59955 exists.

## Other vulnerabilities in coollabsio coolify

- [CVE-2025-59157](https://insights.sbomify.com/CVE-2025-59157/): Coolify has Git Repository RCE (critical 10.0)
- [CVE-2025-64420](https://insights.sbomify.com/CVE-2025-64420/): Coolify members can see private key of root user (critical 10.0)
- [CVE-2025-66209](https://insights.sbomify.com/CVE-2025-66209/): Coolify Vulnerable to Authenticated Remote Code Execution via Command Injection in Database Backup (critical 10.0)
- [CVE-2025-22609](https://insights.sbomify.com/CVE-2025-22609/): Coolify Vulnerable to Private Key Hijacking / Remote Command Execution (RCE) (critical 10.0)
- [CVE-2025-22611](https://insights.sbomify.com/CVE-2025-22611/): Coolify vulnerable to Privilege Escalation resulting in Remote Command Execution (RCE) (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59955 and fix it if it is affected.

What it is: CVE-2025-59955 is a medium-severity vulnerability in coollabsio coolify, published on 5 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59955 exists.

Affected product: coollabsio coolify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59955/ (Markdown: https://insights.sbomify.com/CVE-2025-59955/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59955
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59955
- OSV: https://osv.dev/vulnerability/CVE-2025-59955

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59955/
Summaries are generated and may contain mistakes; the official description above is the record.