dbcve.org
CoolifyApplication · Coollabs

CVE-2025-22612

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.374, the missing authorization allows an authenticated user to retrieve any existing private keys on a coolify instance in plain text. 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 execute arbitrary commands on the remote server. Version 4.0.0-beta.374 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

Missing authorization in Coolify versions prior to 4.0.0-beta.374 allows any authenticated user to retrieve any existing private keys on the instance in plain text. If the attacker matches the target server's IP/domain, port (typically 22), and user (root), they can execute arbitrary commands on the remote server.

MitigationUpgrade Coolify to version 4.0.0-beta.374 or later which includes 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. Identify Coolify version
    Access the Coolify admin panel or check the installed package/version. Compare the installed version against the vulnerable range: versions prior to 4.0.0-beta.374 and version 4.0.0 are affected.
    Affected if The installed version is < 4.0.0-beta.374 or equals exactly 4.0.0 (the initial release)
  2. Check for stored private keys
    In the Coolify UI, navigate to the SSH Keys or Private Keys section under project settings, server configuration, or destination settings. Look for any saved private keys used for SSH connections.
    Affected if Any private keys are stored in the Coolify instance and the version is vulnerable
  3. Verify SSH target configuration
    Review configured servers or destinations in Coolify. Check if any servers are configured with IP/domain, port 22, and root user for remote command execution.
    Affected if SSH targets with matching IP/domain, port 22, and root user are configured in Coolify and the version is vulnerable
  4. Confirm multi-user environment
    Check if more than one user account exists in the Coolify instance. The vulnerability allows ANY authenticated user to access keys they should not have access to.
    Affected if Multiple user accounts exist in Coolify and the version is vulnerable

A user is affected if Coolify version is < 4.0.0-beta.374 or exactly 4.0.0, and the instance has stored private keys or configured SSH targets accessible to any authenticated user.

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.374 or later which includes the authorization fix.

Recommended fix High confidence

4.0.0-beta.374 or later stable release

  1. Verify current Coolify version by checking the instance admin panel or command line
  2. Backup all current configurations, private keys, and data before upgrading
  3. Upgrade Coolify to version 4.0.0-beta.374 or later release
  4. After upgrade, verify that the authorization fix is applied by attempting to access resources outside your authorized scope (should be denied)
  5. Review all private keys and SSH credentials that were exposed, consider rotating them as a precaution
Caveat Review release notes for 4.0.0-beta.374 for any configuration or feature changes before upgrading production instances

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

Fix this in Coolify Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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