CVE-2026-34034: Coolify Sentinel Command Injection – Patch Guide & Risk Analysis

Technical summary

CVE-2026-34034 is a command injection flaw (CWE-78) in Coolify's Sentinel token handling mechanism. The vulnerability stems from insufficient validation of the sentinel_token setting before it is used in shell command construction. An authenticated attacker with Sentinel configuration privileges can embed shell metacharacters and command sequences into the token value. When Sentinel is restarted, the unsanitized token is executed as part of a shell command, allowing arbitrary command execution in the context of the Coolify process. The attack surface is limited to users with explicit server Sentinel access, but the impact is unrestricted code execution on the underlying host.

Business impact

Organizations self-hosting Coolify face a critical operational risk if team members with legitimate Sentinel access—such as DevOps engineers or infrastructure administrators—are compromised or act maliciously. Successful exploitation could lead to complete host compromise, allowing attackers to exfiltrate sensitive data, modify application configurations, pivot to other systems on the network, or establish persistent backdoors. For multi-tenant or shared Coolify instances, the blast radius extends to all managed servers and applications. Incident response and forensic analysis would be significantly complicated if Coolify processes gain elevated privileges on the host.

Affected systems

Coolify versions prior to 4.0.0-beta.466 are affected. The vulnerability applies universally across all platforms (Linux, Windows, macOS) where Coolify is self-hosted. Only instances with Sentinel enabled and configured are vulnerable; the attack requires an authenticated user with access to modify server Sentinel settings. Open-source deployments and organizations running Coolify in containerized or on-premises environments are directly in scope.

Exploitability

The vulnerability requires authentication and explicit access to Sentinel configuration, limiting casual exploitation. However, the barrier to attack is low once an attacker gains valid credentials—no special tools, race conditions, or timing constraints are needed. A simple modification to the sentinel_token field with embedded shell syntax (e.g., `token'; malicious_command; echo '`) and triggering a Sentinel restart executes the injected command. The CVSS score of 8.8 (HIGH) reflects the requirement for authentication (PR:L) but high impact across confidentiality, integrity, and availability. This is not actively exploited in known public POCs or KEV lists, but the attack is straightforward to execute and difficult to detect if not logged properly.

Remediation

Upgrade to Coolify version 4.0.0-beta.466 or later immediately. This patch includes proper input validation and sanitization of the sentinel_token setting before it is incorporated into shell commands. Organizations unable to update immediately should restrict access to server Sentinel settings to a minimal set of highly trusted administrators and monitor Sentinel restart events and process execution logs for anomalies. Consider disabling Sentinel if it is not actively required.

Patch guidance

Apply the fix by upgrading to version 4.0.0-beta.466 or later. Verify the upgrade is complete by checking the Coolify version number in the UI or via API. Since this is a beta release, plan for potential instability and conduct testing in a non-production environment first. Review any custom shell scripts or integrations that may depend on Sentinel token handling to ensure they remain compatible. After upgrade, restart all Sentinel instances to activate the fix.

Detection guidance

Monitor Coolify application logs and system-level audit logs for unusual Sentinel restart events, especially those followed by unexpected process spawning or system command execution. Search for shell metacharacters in Sentinel token settings via configuration exports or database inspection (if accessible). Implement alerting on process execution events from Coolify service accounts, particularly commands that invoke shells or system utilities outside normal operational patterns. Use container or host-level security tools to flag command injection signatures in Coolify process execution chains.

Why prioritize this

Although authentication is required, the ease of exploitation, high impact, and prevalence of Coolify in DevOps and infrastructure automation toolchains warrant immediate remediation. The vulnerability sits at the intersection of infrastructure control and code execution, making it a high-value target in supply chain and insider threat scenarios. Delaying patching increases the window of exposure for organizations with security-conscious teams that might be targeted for lateral movement.

Risk score, explained

The CVSS 3.1 score of 8.8 (HIGH) is driven by the unrestricted impact on confidentiality, integrity, and availability (C:H/I:H/A:H), combined with network accessibility (AV:N) and low complexity (AC:L). The privilege requirement (PR:L) prevents a score of 9.0 or above, but the lack of user interaction (UI:N) and single-system scope (S:U) reflect a direct and complete compromise of the affected host. No sandbox or privilege boundary mitigates the execution context, making this a genuine critical risk to any instance where Sentinel is in use.

Frequently asked questions