dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-34038

CRITICAL · 9.9 CVSS v3.1 Published 2026-07-06
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 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, an authenticated remote command injection vulnerability in application deployment handling allows users with application write permissions to achieve remote code execution and exfiltrate sensitive environment variables through deployment logs via fields such as dockerfile_location and deployment commands. 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

Authenticated command injection vulnerability in Coolify's application deployment handling allows users with application write permissions to inject malicious commands through fields such as dockerfile_location and deployment commands, achieving remote code execution and exfiltrating sensitive environment variables exposed in deployment logs.

MitigationUpgrade to Coolify version 4.0.0-beta.469 or later. Until patched, restrict application write permissions to only trusted users and monitor deployment logs for suspicious command patterns.

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify installed Coolify version
    Access the Coolify dashboard and navigate to the Settings or About page to view the current version number. Alternatively, check the container logs or the coolify version command if available.
    Affected if The installed version is lower than 4.0.0-beta.469 (the patched version).
  2. Review application write permissions
    Navigate to the Coolify admin panel and check which users or teams have write permissions for applications. Look for the 'Write' or 'Edit' permission level on application resources.
    Affected if Any untrusted user or team has application write permissions enabled.
  3. Inspect deployment configuration for suspicious fields
    Review application deployment settings, specifically the dockerfile_location field and any custom deployment command fields. Check if these fields accept user-supplied input without sanitization.
    Affected if The dockerfile_location or deployment command fields accept and execute unsanitized user input.
  4. Examine deployment logs for command injection patterns
    Access the deployment logs in the Coolify dashboard or log files. Search for unusual commands, shell metacharacters, or unexpected environment variable references.
    Affected if Logs contain commands or environment variable exfiltration attempts that were not intentionally configured.

A user is affected if running a Coolify version below 4.0.0-beta.469 with any untrusted user having application write permissions, or if deployment logs show evidence of unauthorized command execution.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to Coolify version 4.0.0-beta.469 or later. Until patched, restrict application write permissions to only trusted users and monitor deployment logs for suspicious command patterns.

Recommended fix Moderate confidence

4.0.0-beta.469

  1. 1. Back up your current Coolify installation and all application data.
  2. 2. Upgrade Coolify to version 4.0.0-beta.469 or later.
  3. 3. After upgrading, review all existing applications that have custom dockerfile_location or deployment commands configured.
  4. 4. Audit deployment logs from before the upgrade to check for any unauthorized access or environment variable exfiltration.
  5. 5. Rotate any sensitive credentials or API keys that may have been exposed through the vulnerability.
  6. 6. Ensure users with application write permissions are limited to trusted individuals only.
Caveat Beta version - may contain other breaking changes; test in staging before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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