{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64419 exists.","fix":"No fix has been published for CVE-2025-64419 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-64419 is a critical command injection vulnerability in coollabsio coolify, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-64419 and fix it if it is affected.\n\nWhat it is: CVE-2025-64419 is a critical command injection vulnerability in coollabsio coolify, published on 5 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64419 exists.\n\nAffected product: coollabsio coolify. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-64419/ (Markdown: https://insights.sbomify.com/CVE-2025-64419/index.md)","id":"CVE-2025-64419","markdown":"https://insights.sbomify.com/CVE-2025-64419/index.md","name":"CVE-2025-64419","record":{"aliases":["GHSA-234r-xrrg-m8f3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Coolify self-hosting platform","requires_auth":"none","summary":"Attackers can execute arbitrary commands as root on Coolify instances by crafting malicious docker-compose parameters in a repository.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"coolify","vendor":"coollabs"}],"cvss":{"score":9.7,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to version 4.0.0-beta.445, parameters coming from docker-compose.yaml are not sanitized when used in commands. If a victim user creates an application from an attacker repository (using build pack \"docker compose\"), the attacker can execute commands on the Coolify instance as root. Version 4.0.0-beta.445 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Coolify vulnerable to command injection via docker-compose.yaml parameters","id":"CVE-2025-64419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Coolify members can see private key of root user","id":"CVE-2025-64420"},"packages":[],"prev":{"headline":"Apache Causeway: Java deserialization vulnerability to authenticated attackers","id":"CVE-2025-64408"},"products":["coolify"],"published":"2026-01-05","related":[{"cvss_score":10,"headline":"Coolify has Git Repository RCE","id":"CVE-2025-59157","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":10,"headline":"Coolify members can see private key of root user","id":"CVE-2025-64420","kev_date_added":null,"published":"2026-01-05"},{"cvss_score":10,"headline":"Coolify Vulnerable to Authenticated Remote Code Execution via Command Injection in Database Backup","id":"CVE-2025-66209","kev_date_added":null,"published":"2025-12-23"},{"cvss_score":10,"headline":"Coolify Vulnerable to Private Key Hijacking / Remote Command Execution (RCE)","id":"CVE-2025-22609","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":10,"headline":"Coolify vulnerable to Privilege Escalation resulting in Remote Command Execution (RCE)","id":"CVE-2025-22611","kev_date_added":null,"published":"2025-01-24"},{"cvss_score":10,"headline":"Coolify Vulnerable to Private Key Enumeration on Onboarding resulting in Remote Command Execution (RCE)","id":"CVE-2025-22612","kev_date_added":null,"published":"2025-01-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-05","vendors":["coollabsio"]},"summary":"Attackers can execute arbitrary commands as root on Coolify instances by crafting malicious docker-compose parameters in a repository.","url":"https://insights.sbomify.com/CVE-2025-64419/"}