Vulnerability in Coolify (CVE-2026-27883)
Summary
Vulnerability in Coolify (CVE-2026-27883). Risk of unauthorized operations or information disclosure. Exploitable via GET /api/v1/deployments/{uuid}. Mitigation: upgrade to 4.0.0-beta.464 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.464, the GET /api/v1/deployments/{uuid} endpoint allows any authenticated user to access deployment details belonging to any team, bypassing team-based authorization. The $teamId is extracted from the authentication token but never used to scope the database query. This vulnerability is fixed in 4.0.0-beta.464.
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-27883 has been found in Coolify.
Attackers can target a specific entry point like GET /api/v1/deployments/{uuid} over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.0/10.
What to do: upgrade Coolify to 4.0.0-beta.464 or later.
If unsure, ask your IT team or search "Coolify CVE-2026-27883" on the vendor's site.
CVE-2026-27883 (Coolify) — CWE-639 / CVSS v3 5.0
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/v1/deployments/{uuid}
Patched: 4.0.0-beta.464 — 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. Attackers reach the vulnerable code path via GET /api/v1/deployments/{uuid}.
Check the vendor advisory for the affected versions of Coolify. Attack surface: GET /api/v1/deployments/{uuid}.
Severity: Medium (CVSS 5.0/10). Risk of unauthorized operations or information disclosure.
Update to 4.0.0-beta.464.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/deployments/{uuid} requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/deployments/{uuid}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/deployments/{uuid}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Coolify to 4.0.0-beta.464ステージング環境で 4.0.0-beta.464 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/deployments/{uuid} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov