Cross-team disclosure via unscoped deployment lookup
Published Jun 30, 2026 · Updated Jun 30, 2026
Authorization bypass in Coolify before 4.0.0-beta.464 allows remote authenticated users to read other teams' deployment details. DeployController.php's deployment_by_uuid method extracts the token's team identifier but queries ApplicationDeploymentQueue only by the supplied deployment UUID. A valid API token and a victim deployment UUID are required; exposed records include application, server, commit, URL, and possibly sensitive build-log data.
Summary
What happened
Authorization bypass in Coolify before 4.0.0-beta.464 allows remote authenticated users to read other teams' deployment details. DeployController.php's deployment_by_uuid method extracts the token's team identifier but queries ApplicationDeploymentQueue only by the supplied deployment UUID. A valid API token and a victim deployment UUID are required; exposed records include application, server, commit, URL, and possibly sensitive build-log data.
The record
- CVE
- CVE-2026-27883
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- coolLabs
- Product
- Coolify
- Classifications
- CWE-639, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 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.464
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 retrieval 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