dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-27957

HIGH · 8.8 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 →
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.464, an authenticated command injection vulnerability in the CA Certificate management feature allows any authenticated user to execute arbitrary commands as the configured SSH user on the managed server host. As the SSH user typically would have to either be root or part of the docker group for Coolify to function as intended, this provides complete compromise of the managed server and associated docker containers. 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

An authenticated command injection vulnerability in Coolify's CA Certificate management feature allows any authenticated user to execute arbitrary commands as the configured SSH user on managed server hosts. Since the SSH user typically has root or docker group privileges for normal operation, this enables complete compromise of the managed server and associated docker containers.

MitigationUpgrade Coolify to version 4.0.0-beta.464 or later to remediate this vulnerability. Until patched, limit user access and monitor for suspicious command execution.

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. Identify Coolify installation and version
    Check the Coolify version by accessing the admin panel or running 'coolify --version' if CLI is available. Also check /opt/coolify/versions.json or similar version files in the installation directory.
    Affected if The installed version is earlier than 4.0.0-beta.464 and the CA Certificate feature is accessible to authenticated users.
  2. Verify CA Certificate management feature
    In the Coolify web interface, navigate to the CA Certificate management section under Settings or Security settings. Check if the feature is present and accessible.
    Affected if The CA Certificate feature exists and users with standard authentication can access it.
  3. Check SSH configuration for managed servers
    Review the SSH connection settings for managed servers in Coolify. Look at which SSH user is configured and whether it has root or docker group privileges.
    Affected if The configured SSH user has root privileges or is a member of the docker group.
  4. Audit for suspicious command execution
    Review system logs (/var/log/auth.log, journalctl, or Coolify's own logs) for any unexpected commands or scripts executed from Coolify servers, particularly around CA Certificate operations.
    Affected if There are command execution logs that correspond to CA Certificate operations from users who should not have that access.

A user is affected if running a Coolify version earlier than 4.0.0-beta.464 with the CA Certificate management feature accessible to authenticated users, where the configured SSH user has elevated privileges.

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.464 or later to remediate this vulnerability. Until patched, limit user access and monitor for suspicious command execution.

Recommended fix High confidence

4.0.0-beta.464

  1. 1. Back up your current Coolify installation and configuration
  2. 2. Upgrade Coolify to version 4.0.0-beta.464 or later
  3. 3. Verify the upgrade was successful by logging into the Coolify dashboard
  4. 4. Confirm the CA Certificate management feature is accessible and functioning properly
  5. 5. Test that the command injection vulnerability is no longer present

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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