Vulnerability in Coolify (CVE-2026-57498)
Summary
Vulnerability in Coolify (CVE-2026-57498). Confidential information can be exposed externally. Mitigation: upgrade to 4.0.0-beta.474 or later.
Original description
The description as published by the source.
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.474, Coolify's API controllers consistently validate server ownership with Server::whereTeamId($teamId) before any operation. However, multiple Livewire web UI components accept server_id and destination_uuid from URL query parameters without any team ownership validation, allowing cross-team resource deployment. This vulnerability is fixed in 4.0.0-beta.474.
Source: NIST National Vulnerability Database NVD GitHub Advisory
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-2026-57498 has been found in Coolify.
Confidential information can be exposed externally. CVSS score: 9.6/10.
What to do: upgrade Coolify to 4.0.0-beta.474 or later.
If unsure, ask your IT team or search "Coolify CVE-2026-57498" on the vendor's site.
CVE-2026-57498 (Coolify) — CWE-639 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.0.0-beta.474 — apply immediately
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-639) exists in Coolify.
Check the vendor advisory for the affected versions of Coolify.
Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally.
Update to 4.0.0-beta.474.
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. Run grep -r 'Coolify' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Coolify' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Coolifyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Coolify to 4.0.0-beta.474ステージング環境で 4.0.0-beta.474 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov