Quick answers
- Is CVE-2026-57498 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57498 being exploited in the wild.
- How severe is CVE-2026-57498?
- Critical severity, with a CVSS score of 9.6, published 29 June 2026.
- Which products and versions are affected?
- Coollabs Coolify < 4.0.0-beta.474.
- Is there a fix for CVE-2026-57498?
- A patch was published on 2026-06-28: Vulnerability fixed in version 4.0.0-beta.474 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57498 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-57498?
- Check whether you run Coollabs Coolify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Coolify prior to version 4.0.0-beta.474 is vulnerable to an Insecure Direct Object Reference (IDOR) and missing authorization checks within several Livewire web UI components. While the API controllers correctly validate server ownership, components such as 'app/Livewire/Project/Resource/Create.php' and the boarding flow accept 'server_id' and 'destination_uuid' directly from URL query parameters without verifying team ownership. An authenticated attacker can exploit this by providing the ID or UUID of a server belonging to a different team, enabling them to deploy containers to that server or execute SSH commands via the boarding flow's validation process. The vulnerability is fixed in version 4.0.0-beta.474 by ensuring all server and destination lookups are scoped to the current team.
Affected products
- coollabsio Coolify < 4.0.0-beta.474
Timeline
- 2026-06-28: advisory: GitHub Security Advisory published by vendor
- 2026-06-29: disclosed: CVE published to NVD
- 2026-06-28: patched: Vulnerability fixed in version 4.0.0-beta.474