dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-34158

HIGH · 8.8 CVSS v3.1 Published 2026-07-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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.469, the executeInDocker() helper wraps user-controlled commands in single quotes without escaping embedded single quotes. Attackers who can edit application settings can inject a single quote into docker_compose_custom_build_command or docker_compose_custom_start_command to break out of the quoted context and execute arbitrary commands on the managed server host during deployments, escaping the intended Docker container confinement. This issue is fixed in version 4.0.0-beta.469.

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 versions before 4.0.0-beta.469 improperly wraps user-controlled commands from docker_compose_custom_build_command and docker_compose_custom_start_command settings in single quotes without escaping embedded single quotes. Attackers with access to edit application settings can inject a single quote to break out of the quoted context and execute arbitrary commands on the host server during deployments, escaping Docker container confinement.

MitigationUpgrade Coolify to version 4.0.0-beta.469 or later. Until then, restrict access to application settings configuration to trusted users only and audit existing settings for malicious content.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Check Coolify version
    Locate the Coolify installation and determine its version number. This is typically visible in the web UI dashboard or obtainable via CLI commands provided by the Coolify installation method.
    Affected if The installed version is before 4.0.0-beta.469 (e.g., 4.0.0-beta.450, 4.0.0-beta.400, 3.x.x, etc.)
  2. Identify application settings access
    Review user permissions and access controls to determine which users or roles can edit application settings, specifically the docker_compose_custom_build_command and docker_compose_custom_start_command configuration fields.
    Affected if Untrusted users or roles have permissions to modify these application-level settings.
  3. Inspect docker_compose_custom_build_command setting
    For each application in Coolify, examine the docker_compose_custom_build_command setting value (if configured). Look for the presence of unescaped single quote characters that could indicate injection attempts.
    Affected if This setting contains any command with single quotes that were not properly escaped by the application.
  4. Inspect docker_compose_custom_start_command setting
    For each application in Coolify, examine the docker_compose_custom_start_command setting value (if configured). Search for unescaped single quote characters that could break out of the quoted context.
    Affected if This setting contains any command with single quotes that were not properly escaped by the application.

You are affected if your Coolify version is before 4.0.0-beta.469 AND untrusted users can edit application settings containing docker_compose_custom_build_command or docker_compose_custom_start_command, or if those settings already contain suspicious single quote characters.

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 Coolify to version 4.0.0-beta.469 or later. Until then, restrict access to application settings configuration to trusted users only and audit existing settings for malicious content.

Recommended fix High confidence

4.0.0-beta.469

  1. Upgrade Coolify to version 4.0.0-beta.469 or later

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34158 — 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-34158 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