Security readout for executives and security teams
Plain-English summary
An authenticated low-privilege Coolify user could abuse project deployment settings to make Docker mount the host root filesystem, potentially giving full root control of the server. This is critical because Coolify commonly manages application infrastructure and secrets.
Executive priority
Treat this as urgent for any Coolify instance with multiple users or shared team access. Successful exploitation could hand an insider or compromised member account root control of the deployment server.
Technical view
The CVE describes Docker Compose directive injection in Coolify application deployment before the patched beta release. Insufficient validation allows low-privileged authenticated users to supply malicious service definitions, leading to remote code execution and host compromise through Docker filesystem mounting.
Likely exposure
Organizations running Coolify versions before the vendor-patched release are exposed if untrusted or less-trusted users can create projects or applications. Internet exposure increases risk, but authentication is required by the CVE description.
Exploitation context
The source bundle lists a public technical/exploit repository, so practical knowledge may be available. KEV is false, and the provided sources do not state active exploitation in the wild.
Researcher notes
Evidence is strongest for authenticated low-privilege abuse through deployment workflow input validation. The affected range is described as prior to v4.0.0-beta.420.6, while the patch reference points to v4.0.0-beta.420.7; confirm exact fixed versions with vendor release notes.
Mitigation direction
- Upgrade Coolify to a vendor-patched release; the CVE references v4.0.0-beta.420.7.
- Review Coolify release notes and vendor guidance before deploying the fix.
- Restrict project creation and deployment rights to trusted administrators.
- Audit existing projects for unexpected Docker Compose directives or host filesystem mounts.
- Rotate secrets if compromise of the Coolify host is suspected.
Validation and detection
- Inventory all Coolify instances and record their exact versions.
- Confirm whether low-privileged members can create projects or deployments.
- Check deployment definitions for host root filesystem mounts or unusual privileged service settings.
- Review Coolify and host logs for suspicious project creation or deployment activity.
- Verify the upgraded instance blocks unsafe Docker Compose directives.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-20: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-34159 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/coollabsio/coolify/releases/tag/v4.0.0-beta.420.7CVE reference, VulnCheck · vendor-advisory, patch
- https://coolify.io/CVE reference, VulnCheck · product
- https://github.com/Eyodav/CVE-2025-34159CVE reference, VulnCheck · technical-description, exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Input Validation
Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.