# CVE-2026-27883: Coolify: IDOR in Deployment API - Cross-Team Deployment Information Disclosure

> An authenticated user can access deployment details from any team by bypassing team-based authorization checks in the API.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-f6h4-qx26-76jv

## What is CVE-2026-27883?

CVE-2026-27883 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Coolify 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-27883?


## How do I fix CVE-2026-27883?

No fix has been published for CVE-2026-27883 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-27883 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27883 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27883 and fix it if it is affected.

What it is: CVE-2026-27883 is a medium-severity missing authorization vulnerability in coollabsio coolify, published on 30 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27883 exists.

Affected product: coollabsio coolify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-27883/ (Markdown: https://insights.sbomify.com/CVE-2026-27883/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27883
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27883
- OSV: https://osv.dev/vulnerability/CVE-2026-27883

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27883/
Summaries are generated and may contain mistakes; the official description above is the record.