OS Command Injection in Coolify (CVE-2026-27957)
Summary
OS command injection in Coolify (CVE-2026-27957). Successful exploitation can lead to full system takeover. 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, an authenticated command injection vulnerability in the CA Certificate management feature allows any authenticated user to execute arbitrary commands as the configured SSH user on the managed server host. As the SSH user typically would have to either be root or part of the docker group for Coolify to function as intended, this provides complete compromise of the managed server and associated docker containers. 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-27957 has been found in Coolify.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/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-27957" on the vendor's site.
CVE-2026-27957 (Coolify) — CWE-78 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
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.
OS command injection (CWE-78) exists in Coolify.
Check the vendor advisory for the affected versions of Coolify.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
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 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.464ステージング環境で 4.0.0-beta.464 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov