CVE-2026-27883
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 `GET /api/v1/deployments/{uuid}` endpoint allows any authenticated user to access deployment details belonging to any team, bypassing team-based authorization. The $teamId is extracted from the authentication token but never used to scope the database query. This vulnerability is fixed in 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 GET /api/v1/deployments/{uuid} endpoint in Coolify prior to 4.0.0-beta.464 has an IDOR vulnerability where the teamId extracted from the authentication token is not used to scope the database query, allowing any authenticated user to view deployment details belonging to any team.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N
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.
-
Confirm Coolify installationCheck for Coolify by looking for its web interface (typically on port 8000) or by running 'docker ps' to see coolify containersAffected if Coolify is running and accessible via network
-
Determine installed versionCheck the Coolify web interface footer for version number, or run 'docker ps' and inspect the coolify container image tagAffected if Version is displayed as anything prior to 4.0.0-beta.464 (e.g., 4.0.0-beta.463, 4.0.0-beta.400, etc.)
-
Verify API endpoint is accessibleAttempt to reach GET /api/v1/deployments/{uuid} endpoint using curl or similar: curl -k https://your-coolify-host/api/v1/deployments/any-uuid -H 'Authorization: Bearer YOUR_TOKEN'Affected if API returns HTTP 200 or 404 (rather than 401/403), indicating the endpoint exists and accepts authenticated requests
-
Check authentication is enforced but not team-scopedLog in as a regular user belonging to Team A, then attempt to access a deployment UUID that belongs to Team B; observe if deployment details are returned without authorization errorAffected if Request succeeds and returns deployment data belonging to a different team, indicating the teamId is not being used to scope the query
User is affected if running Coolify version earlier than 4.0.0-beta.464 and the API endpoint is accessible to authenticated users who should not have cross-team visibility.
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. If immediate upgrade is not feasible, implement network-level access controls restricting API access to authorized team members only.
4.0.0-beta.464
- Upgrade Coolify to version 4.0.0-beta.464 or later to address the IDOR vulnerability in the /api/v1/deployments/{uuid} endpoint
- Verify that the team-based authorization is now properly enforced by testing access to deployment resources across different teams
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27883 — 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-27883 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