dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-27881

MEDIUM · 5.0 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
56/100
Remediation priority · Elevated
Remotely reachable Zero-click 7 weeks old

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 · unedited
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.464, `GET /api/v1/deployments/{uuid}` in DeployController.php retrieves deployment details without validating that the deployment belongs to the authenticated user's team. Any authenticated API user can read deployment records from other teams by providing a valid deployment UUID. 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 confidence

This is an Insecure Direct Object Reference (IDOR) vulnerability in Coolify's deployment API. The endpoint GET /api/v1/deployments/{uuid} in DeployController.php fails to validate that the requested deployment belongs to the authenticated user's team, allowing any authenticated API user to read deployment records from other teams by providing a valid deployment UUID.

MitigationUpgrade to Coolify version 4.0.0-beta.464 or later, which includes proper team ownership validation in the deployment retrieval endpoint.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Coolify installation and version
    Check the Coolify service version by accessing the health endpoint or checking the container/image version. Common paths: check the Docker container tag, helm chart version, or query the API health endpoint at GET /api/v1/health if available.
    Affected if The installed version is below 4.0.0-beta.464 (the fixed release). Compare your running version against this baseline.
  2. Verify API authentication is enabled
    Confirm that the Coolify API requires authentication. Check if API tokens are configured and required for endpoint access. The IDOR only affects authenticated users, so an unauthenticated API would not be vulnerable.
    Affected if API authentication is enforced and you have valid API credentials for at least one team.
  3. Confirm deployment API endpoint exists
    Test that the endpoint GET /api/v1/deployments/{uuid} is accessible. Send an authenticated request to this endpoint using a valid deployment UUID from your own team to verify the endpoint responds.
    Affected if The deployment retrieval endpoint is reachable and returns deployment data for authenticated requests.
  4. Test for cross-team deployment access
    Using API credentials from one team, attempt to retrieve a deployment belonging to a different team by providing that deployment's UUID in GET /api/v1/deployments/{uuid}. If you receive deployment details for a team you do not belong to, the IDOR is present.
    Affected if The API returns deployment data for a UUID belonging to a different team without rejecting the request based on team ownership validation.

You are affected if running a Coolify version below 4.0.0-beta.464 with API authentication enabled, and the GET /api/v1/deployments/{uuid} endpoint returns deployment data for UUIDs outside your authenticated team scope.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Coolify version 4.0.0-beta.464 or later, which includes proper team ownership validation in the deployment retrieval endpoint.

Recommended fix High confidence

4.0.0-beta.464 or later stable release

  1. 1. Check current Coolify installation version using the admin UI or CLI
  2. 2. Create a complete backup of the Coolify database and configuration
  3. 3. Upgrade Coolify to version 4.0.0-beta.464 or later
  4. 4. After upgrade, verify the fix by attempting to access a deployment UUID from another team (should now return 403 Forbidden)
  5. 5. Confirm normal deployment access within your team still works correctly
Caveat This is a beta version upgrade; beta releases may contain unstable features and breaking changes; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27881 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27881 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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