CVE-2026-34037
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCoolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.464, the cloneTo() Livewire action in ResourceOperations.php authorizes the source resource but resolves destination resources with unscoped Eloquent lookups, allowing an authenticated user to clone resources into destinations owned by other teams and access cross-tenant resources. This issue is fixed in version 4.0.0-beta.464.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe cloneTo() Livewire action in ResourceOperations.php properly authorizes source resources but resolves destination resources using unscoped Eloquent queries, allowing authenticated users to clone resources to destinations owned by other teams and achieve unauthorized cross-tenant data access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Coolify installation and versionLocate the Coolify installation and determine its version number. Check package.json, composer.json, or the Coolify admin panel for the installed version.Affected if The installed version is older than 4.0.0-beta.464 and contains the cloneTo() Livewire action in ResourceOperations.php.
-
Locate ResourceOperations.phpFind the ResourceOperations.php file in the codebase, typically in a Livewire actions or operations directory. Search for a file containing the cloneTo() method.Affected if The file exists and contains the cloneTo() method implementation.
-
Inspect cloneTo() method for unscoped queriesExamine the cloneTo() method code. Look for Eloquent query calls on destination resources that do not include team_id or tenant scoping constraints. Search for methods like 'withoutGlobalScope' or absence of 'where('team_id', ...)' clauses on destination model queries.Affected if The destination resource queries lack team/tenant scoping constraints, allowing cross-tenant resource resolution.
-
Verify authentication and resource accessConfirm that authenticated users can access the cloneTo() action through the application interface. Test whether a user from one team can invoke this action on resources belonging to another team.Affected if The action is accessible to authenticated users without proper destination resource authorization checks.
An environment is affected if running a Coolify version before 4.0.0-beta.464 where the cloneTo() method in ResourceOperations.php uses unscoped queries to resolve destination resources, enabling cross-tenant access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Coolify to version 4.0.0-beta.464 or later, which adds proper tenant scoping to destination resource lookups in the cloneTo() action.
4.0.0-beta.464
- Upgrade Coolify to version 4.0.0-beta.464 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34037 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34037 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data