Security readout for executives and security teams
Plain-English summary
Coolify before v4.0.0-beta.420.7 can let a low-privileged authenticated user turn a project setup field into host command execution. In business terms, a compromised or malicious member account could lead to full server compromise.
Executive priority
Prioritize remediation immediately for internet-facing or multi-user Coolify deployments. The vulnerability can convert limited authenticated access into full host compromise, affecting confidentiality, integrity, availability, and connected deployment secrets.
Technical view
The issue is command injection in the project deployment workflow through the Git Repository field during project creation. It is mapped to CWE-20 and CWE-78, requires authentication with low-level member privileges, and has CVSS 4.0 score 9.4.
Likely exposure
Organizations running self-hosted Coolify versions earlier than v4.0.0-beta.420.7 are the likely exposed group. Exposure is higher where many team members can create projects or where member accounts are externally compromised.
Exploitation context
The CVE bundle lists a public technical/exploit reference, but KEV is false and the provided sources do not state active exploitation in the wild. Treat exploitability as practical, but do not claim observed exploitation.
Researcher notes
The source bundle supports critical severity, authenticated low-privilege attack requirements, and a vendor patch release. It does not provide confirmed exploitation-in-the-wild evidence. Exact affected-version metadata appears incomplete, so use the stated pre-v4.0.0-beta.420.7 boundary.
Mitigation direction
- Upgrade Coolify to v4.0.0-beta.420.7 or later.
- Review vendor release notes and guidance before production rollout.
- Restrict project creation to trusted users until patched.
- Audit low-privileged member accounts for unnecessary access.
- Rotate host and deployment secrets if compromise is suspected.
Validation and detection
- Inventory all Coolify instances and record exact versions.
- Confirm each instance is v4.0.0-beta.420.7 or later.
- Review project creation permissions for low-level members.
- Inspect logs for suspicious project creation or repository field values.
- Check host integrity if untrusted users had project creation rights.
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-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter 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 lookupCVE-2025-34161 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-34161CVE 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.