Vulnerability in /api/v1/teams/{team_id}/members (CVE-2025-59955)
Summary
Vulnerability in /api/v1/teams/{team_id}/members (CVE-2025-59955). Confidential information can be exposed externally. Exploitable via email_change_code.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-59955 has been found in /api/v1/teams/{team_id}/members.
Attackers can target a specific entry point like email_change_code over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "/api/v1/teams/{team_id}/members CVE-2025-59955" on the vendor's site.
CVE-2025-59955 (/api/v1/teams/{team_id}/members) — CWE-201 / CVSS v3 5.7
Attack vector: remote (network-reachable)
Attack surface: email_change_code
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-201) exists in /api/v1/teams/{team_id}/members. Attackers reach the vulnerable code path via email_change_code.
Check the vendor advisory for the affected versions of /api/v1/teams/{team_id}/members. Attack surface: email_change_code.
Severity: Medium (CVSS 5.7/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで /api/v1/teams/{team_id}/members を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit security-advisories@github.com