dbcve.org
CoolifyApplication · Coollabs

CVE-2025-22609

CRITICAL · 10.0 CVSS v3.1 Published 2025-01-24
Fix available
A fix is available. Upgrade to 4.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 version 4.0.0-beta.361, the missing authorization allows any authenticated user to attach any existing private key on a coolify instance to his own server. If the server configuration of IP / domain, port (most likely 22) and user (root) matches with the victim's server configuration, then the attacker can use the `Terminal` feature and execute arbitrary commands on the victim's server. Version 4.0.0-beta.361 fixes the issue.

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

In Coolify prior to version 4.0.0-beta.361, an IDOR/authorization bypass vulnerability allows any authenticated user to attach any existing private key stored on the Coolify instance to their own server. When the attacker's server configuration (IP/domain, port, user) matches a victim's server configuration, the attacker can use the Terminal feature to execute arbitrary commands on the victim's server with the stolen private key's associated privileges.

MitigationUpgrade Coolify to version 4.0.0-beta.361 or later to receive the authorization fix.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CoolifyApplication
Affected:< 4.0.0= 4.0.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed Coolify version
    Check the Coolify web interface footer, or query the API endpoint /api/version, or run 'coolify --version' from the server CLI if available
    Affected if The version is 4.0.0 or any version prior to 4.0.0-beta.361
  2. Verify authentication is enabled
    Check if user authentication is configured in Coolify by reviewing the authentication settings in the web UI under Settings > Authentication or by checking for created user accounts
    Affected if At least one user account exists and authentication is enabled, allowing the IDOR vulnerability to be exploited by that user
  3. Identify stored private keys
    Navigate to the Coolify web UI and review Resources > Private Keys to list all private keys stored on the instance
    Affected if Any private keys are stored on the Coolify instance, as these could be attached to other servers by an authenticated attacker
  4. Review server configurations for configuration overlap
    List all servers in the Coolify web UI under Resources > Servers and note their IP/domain, port, and user settings to identify any servers with matching or similar configurations
    Affected if Multiple servers share identical or very similar IP/domain, port, and user configurations, creating the condition for the attacker's server to match a victim's configuration
  5. Check Terminal feature access
    Verify if the Terminal feature is available and accessible for servers by checking server details in the Coolify web UI
    Affected if The Terminal feature is enabled and accessible, as this is the mechanism through which command execution occurs after the private key is stolen

You are affected if Coolify version is 4.0.0 or any version prior to 4.0.0-beta.361, and there is at least one authenticated user with access to private keys and servers with matching configurations.

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
Upgrade available Upgrade to 4.0.0 or later
Fixed in 4.0.0
Interim mitigation

Upgrade Coolify to version 4.0.0-beta.361 or later to receive the authorization fix.

Recommended fix High confidence

4.0.0-beta.361 or later

  1. Upgrade Coolify to version 4.0.0-beta.361 or later to resolve the missing authorization vulnerability
  2. After upgrading, verify the fix by reviewing that private keys can no longer be attached to servers without proper authorization
  3. Audit server access logs and terminal session logs for any unauthorized access that may have occurred prior to the upgrade
  4. If any suspicious activity is detected, revoke potentially compromised SSH keys and regenerate new keys

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

Fix this in Coolify Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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