dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-27955

MEDIUM · 6.6 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.464, the executeInDocker() helper wraps commands in bash -c '{$command}' without escaping single quotes. User-controlled docker_compose_custom_build_command and docker_compose_custom_start_command fields are interpolated directly, allowing a single quote to break out of the bash -c argument and execute commands on the managed server host (outside the intended Docker container context). This vulnerability is fixed in 4.0.0-beta.464.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The executeInDocker() helper in Coolify wraps commands using bash -c '{$command}' without escaping single quotes. User-controlled docker_compose_custom_build_command and docker_compose_custom_start_command fields are interpolated directly, allowing a single quote to break out of the bash -c argument and execute arbitrary commands on the host server outside the intended Docker container context.

MitigationUpgrade to Coolify 4.0.0-beta.464 or later which implements proper single quote escaping in the executeInDocker() function. If upgrade is not immediately feasible, implement input validation to reject or sanitize single quotes in the affected docker_compose command fields.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Coolify is installed
    Check for Coolify processes or containers: docker ps --filter "name=coolify" or ps aux | grep -i coolify. Also check common installation paths like /opt/coolify, /root/coolify, or look for the coolify service.
    Affected if No Coolify instance found means not affected
  2. Determine the installed Coolify version
    Check the version file or docker image tag. Common locations: cat /opt/coolify/version or docker exec <container> cat /app/version. If using the coolify CLI: coolify --version
    Affected if Version is below 4.0.0-beta.464 (or version cannot be determined and is likely older)
  3. Locate the executeInDocker function
    If you have access to the Coolify source code, search for the executeInDocker function definition: grep -r "executeInDocker" <coolify-source>/ or grep "function executeInDocker" in the codebase
    Affected if The function exists and uses unescaped bash -c with single quotes pattern
  4. Inspect docker_compose_custom_build_command configuration
    Check Coolify project configurations for docker_compose_custom_build_command field. This may be in database, config files, or UI. Query: grep -r "docker_compose_custom_build_command" <config-path>/ or check via Coolify API if accessible
    Affected if This field contains user-controlled input without single quote sanitization
  5. Inspect docker_compose_custom_start_command configuration
    Check Coolify project configurations for docker_compose_custom_start_command field. Similar to above, check database, config files, or UI.
    Affected if This field contains user-controlled input without single quote sanitization

You are affected if Coolify version is below 4.0.0-beta.464 AND the docker_compose_custom_build_command or docker_compose_custom_start_command fields are populated with user-supplied values that could contain single quotes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Coolify 4.0.0-beta.464 or later which implements proper single quote escaping in the executeInDocker() function. If upgrade is not immediately feasible, implement input validation to reject or sanitize single quotes in the affected docker_compose command fields.

Recommended fix High confidence

4.0.0-beta.464

  1. Check current Coolify version installed on the server
  2. Upgrade Coolify to version 4.0.0-beta.464 or later using the standard upgrade procedure for your installation method
  3. Verify the upgrade completed successfully
  4. Confirm the executeInDocker() helper now properly escapes single quotes in docker_compose_custom_build_command and docker_compose_custom_start_command fields
Caveat This is a beta release; ensure proper testing in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27955 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data