CVE-2025-66209
A public proof of concept exists; no exploitation attested.
- Published2025-12-23
- Fixed in4.0.0
- WeaknessCWE-78
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to version 4.0.0-beta.451, an authenticated command injection vulnerability in the Database Backup functionality allows users with application/service management permissions to execute arbitrary commands as root on managed servers. Database names used in backup operations are passed directly to shell commands without sanitization, enabling full remote code execution. Version 4.0.0-beta.451 fixes the issue.
Timeline
dates in UTC- 2025-12-2322:15CVE publishedNVD
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.0 | < 4.0.0 | 4.0.0 | NVD |
| 4.0 | = 4.0.0 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Products declared by the CNA1 product
As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.
- coollabsio coolifyAffected
- = < 4.0.0-beta.451no fix stated
Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-01-06
Fix
- Update Coollabs coolify to 4.0.0
Advisories and patches
- github.comPatch
- github.comRelease Notes
- github.comVendor Advisory
Detection
read 2026-11-01 01:02 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof of concept
- CISA-ADP (SSVC)PoC stated2026-03-17
- PoC-in-GitHub1 repository, unverifiedknown since 2026-11-010xrakan/coolify-cve-2025-66209-66213
- Metasploit modules
- none listed Metasploit Framework
Sources
- CISA-ADPSSVC decisionpoc2026-03-17
- CNACVSS 3.19.9known since 2026-10-23
- NVDCVSS 3.18.8read 2026-10-23
- CNAweakness (CWE)CWE-78known since 2026-10-23
- FIRST EPSSEPSS score3.9 %2026-11-09
- PoC-in-GitHubproof of concept1known since 2026-11-01
Identifiers
- EUVD-2025-204961same flawENISA EUVD · LicenseRef-ENISA-legal-notice
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2025-12-23
- Last Modified
- 2026-10-19
- NVD status
- Modified
Frequently asked questions
What is CVE-2025-66209?
Is CVE-2025-66209 actively exploited?
What is the CVSS score for CVE-2025-66209?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.
Sources for this record
- CVE Program · CVE Program Terms of Use
- ENISA EU Vulnerability Database · ENISA legal notice §1.2 (reproduction authorised, provided the source is acknowledged)
- FIRST EPSS · EPSS terms of use (free use, attribution requested)
- NVD · Public domain (17 U.S.C. § 105) for NVD-authored data; third-party content under its own terms
- PoC-in-GitHub · CC0-1.0
- CISA Vulnrichment · CC0-1.0