Authenticated cross-team deployment via unscoped Livewire lookups
Published Jun 29, 2026 · Updated Jun 29, 2026
Authorization bypass in coolLabs Coolify before 4.0.0-beta.474 allows remote authenticated users to deploy resources across teams. Livewire creation components resolve URL-supplied server_id and destination_uuid values without scoping either lookup to the current team. The same unscoped boarding-flow server lookup runs an SSH command on another team's server, so any Coolify account can cross its team boundary without user interaction.
Summary
What happened
Authorization bypass in coolLabs Coolify before 4.0.0-beta.474 allows remote authenticated users to deploy resources across teams. Livewire creation components resolve URL-supplied server_id and destination_uuid values without scoping either lookup to the current team. The same unscoped boarding-flow server lookup runs an SSH command on another team's server, so any Coolify account can cross its team boundary without user interaction.
The record
- CVE
- CVE-2026-57498
- Published
- Jun 29, 2026
- Updated
- Jun 29, 2026
- Vendor
- coolLabs
- Product
- Coolify
- Classifications
- CWE-862, CWE-639, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 29, 2026CVE publishedPublication date reported by the CVE source.
- Jun 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.0.0-beta.474
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Cross-team deployment HTTP proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo