PatchSiren cyber security CVE debrief
CVE-2026-34158 coollabsio CVE debrief
Coolify, an open-source tool for managing servers, applications, and databases, has a vulnerability prior to version 4.0.0-beta.469. The executeInDocker() helper function does not properly escape user-controlled commands, allowing attackers to inject malicious commands during deployments. This issue is fixed in version 4.0.0-beta.469. The vulnerability allows attackers with the ability to edit application settings to inject a single quote into docker_compose_custom_build_command or docker_compose_custom_start_command, breaking out of the quoted context and executing arbitrary commands on the managed server host during deployments. Users of Coolify should review their deployments and ensure they are running version 4.0.0-beta.469 or later.
- Vendor
- coollabsio
- Product
- coolify
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-07
- Original CVE updated
- 2026-07-07
- Advisory published
- 2026-07-07
- Advisory updated
- 2026-07-07
Who should care
Users of Coolify versions prior to 4.0.0-beta.469 should be aware of this vulnerability and take steps to mitigate it. This includes reviewing their deployments, restricting access to application settings, and monitoring for suspicious activity. Operators, platform administrators, vulnerability management teams, and security teams should review the vulnerability details and assess their exposure.
Technical summary
The executeInDocker() helper function in Coolify wraps user-controlled commands in single quotes without properly escaping embedded single quotes. This allows attackers with the ability to edit application settings to inject a single quote into docker_compose_custom_build_command or docker_compose_custom_start_command, breaking out of the quoted context and executing arbitrary commands on the managed server host during deployments. The vulnerability is fixed in version 4.0.0-beta.469.
Defensive priority
High
Recommended defensive actions
- Upgrade to version 4.0.0-beta.469 or later
- Restrict access to application settings
- Monitor for suspicious activity
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
Evidence is limited; verification of vulnerability details and affected scope is needed. The executeInDocker() helper function in Coolify wraps user-controlled commands in single quotes without properly escaping embedded single quotes. This allows attackers with the ability to edit application settings to inject a single quote into docker_compose_custom_build_command or docker_compose_custom_start_command, breaking out of the quoted context and executing arbitrary commands on the managed server host during deployments. Limited evidence suggests that Coolify versions prior to 4.0.0-beta.469 are affected. Further verification is required to confirm the extent of the vulnerability and potential impact.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-34158 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-34158
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-34158 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-34158
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/coollabsio/coolify/security/advisories/GHSA-j6j2-frv3-g6f7
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.