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

CVE-2026-34592

HIGH · 7.7 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
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.471, Coolify server and project lookups are not scoped to the current team, allowing any authenticated user to access servers and projects belonging to other teams by specifying their IDs directly. This vulnerability is fixed in 4.0.0-beta.471.

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 where Coolify's API endpoints for looking up servers and projects fail to verify that the requested resource belongs to the user's current team. An authenticated attacker can access sensitive infrastructure belonging to other teams by directly specifying resource IDs in API requests.

MitigationUpgrade Coolify to version 4.0.0-beta.471 or later, which implements proper team-scoping validation for all server and project lookups.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/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. Check installed Coolify version
    Run 'coolify --version' or check the Coolify dashboard footer for the version number
    Affected if Version is earlier than 4.0.0-beta.471 (vulnerable versions lack proper team-scoping validation)
  2. Verify multi-team configuration is active
    In Coolify dashboard, navigate to Team Settings or check if multiple teams/workspaces exist in the database
    Affected if More than one team exists in the Coolify instance - this is required for the IDOR to be exploitable
  3. Confirm API access is enabled
    Check if API endpoints are accessible (typically at /api/v1/) and verify authentication tokens are configured for users
    Affected if API access is enabled and users have API tokens - the vulnerability only applies to API requests
  4. Test resource access across teams
    Using an authenticated API token for Team A, attempt a GET request to /api/v1/servers/{server-id} or /api/v1/projects/{project-id} where the resource ID belongs to Team B
    Affected if The API returns successful data for resources belonging to a different team than the authenticated user - indicates the IDOR is present
  5. Inspect API response for team validation
    Review API responses for proper team_id or workspace ownership validation in the returned JSON data
    Affected if API responses do not include team ownership validation or return cross-team data without authorization errors

A Coolify instance is affected if it runs a version before 4.0.0-beta.471, has multiple teams configured, exposes the API, and allows cross-team resource access via direct object reference in API requests.

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 Coolify to version 4.0.0-beta.471 or later, which implements proper team-scoping validation for all server and project lookups.

Recommended fix High confidence

4.0.0-beta.471

  1. 1. Backup your current Coolify installation and data before upgrading.
  2. 2. Identify your current Coolify version by checking the admin panel or running the version command.
  3. 3. Upgrade Coolify to version 4.0.0-beta.471 or later.
  4. 4. After upgrade, verify that team-scoped access controls are working correctly by testing cross-team access attempts.
  5. 5. Review team permissions to ensure users are only assigned to appropriate teams.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34592 — 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-34592 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