# CVE-2025-22605: Coolify OS Command Injection Vulnerability in SSH Command Generation > Authenticated attackers can inject commands to execute arbitrary code on the Coolify container, accessing sensitive data and modifying software behavior. - **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 24 Jan 2025 - **Updated:** 24 Jan 2025 - **Also known as:** GHSA-9wqm-fg79-4748 ## What is CVE-2025-22605? CVE-2025-22605 is a high-severity command injection vulnerability in coollabsio coolify, published on 24 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Starting in version 4.0.0-beta.18 and prior to 4.0.0-beta.253, a vulnerability in the execution of commands on remote servers allows an authenticated user to execute arbitrary code on the local Coolify container, gaining access to data and private keys or tokens of other users/teams. The ability to inject malicious commands into the Coolify container gives authenticated attackers the ability to fully retrieve and control the data and availability of the software. Centrally hosted Coolify instances (open registration and/or multiple teams with potentially untrustworthy users) are especially at risk, as sensitive data of all users and connected servers can be leaked by any user. Additionally, attackers are able to modify the running software, potentially deploying malicious images to remote nodes or generally changing its behavior. Version 4.0.0-beta.253 patches this issue. Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command) ## Which versions are affected by CVE-2025-22605? It affects 1 product. Products: Coollabs Coolify. ## How do I fix CVE-2025-22605? No fix has been published for CVE-2025-22605 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-22605 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22605 exists. ## Other vulnerabilities in coollabsio coolify - [CVE-2025-59157](https://insights.sbomify.com/CVE-2025-59157/): Coolify has Git Repository RCE (critical 10.0) - [CVE-2025-64420](https://insights.sbomify.com/CVE-2025-64420/): Coolify members can see private key of root user (critical 10.0) - [CVE-2025-66209](https://insights.sbomify.com/CVE-2025-66209/): Coolify Vulnerable to Authenticated Remote Code Execution via Command Injection in Database Backup (critical 10.0) - [CVE-2025-22609](https://insights.sbomify.com/CVE-2025-22609/): Coolify Vulnerable to Private Key Hijacking / Remote Command Execution (RCE) (critical 10.0) - [CVE-2025-22611](https://insights.sbomify.com/CVE-2025-22611/): Coolify vulnerable to Privilege Escalation resulting in Remote Command Execution (RCE) (critical 10.0) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-22605 and fix it if it is affected. What it is: CVE-2025-22605 is a high-severity command injection vulnerability in coollabsio coolify, published on 24 Jan 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22605 exists. Affected product: coollabsio coolify. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-22605/ (Markdown: https://insights.sbomify.com/CVE-2025-22605/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22605 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22605 - OSV: https://osv.dev/vulnerability/CVE-2025-22605 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-22605/ Summaries are generated and may contain mistakes; the official description above is the record.