dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-34048

CRITICAL · 9.9 CVSS v3.1 Published 2026-07-07
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 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, terminal websocket bootstrap routes only check authentication and do not enforce terminal authorization, allowing a low-privileged team member to connect to terminal routes and execute commands on team servers. This issue is fixed in version 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

The terminal websocket bootstrap routes in Coolify versions prior to 4.0.0-beta.471 perform authentication checks but fail to enforce terminal authorization, allowing any authenticated team member to connect to terminal routes and execute arbitrary commands on team servers they should not have access to.

MitigationUpgrade Coolify to version 4.0.0-beta.471 or later to implement proper terminal authorization checks. If immediate upgrade is not feasible, consider restricting websocket terminal access at the network layer or temporarily disabling terminal functionality for low-privileged team members.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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 the command to display the current Coolify version (typically 'coolify --version' or check the admin dashboard version display)
    Affected if The installed version is prior to 4.0.0-beta.471 (e.g., 4.0.0-beta.460, 4.0.0-beta.400, etc.)
  2. Verify terminal websocket functionality is accessible
    Attempt to access or enumerate the terminal websocket bootstrap endpoints (typically found at /api/v1/terminal/ or similar websocket paths in the Coolify API)
    Affected if Terminal websocket routes are exposed and accessible to authenticated users without additional authorization checks
  3. Review team member server access assignments
    Examine the team configuration to identify servers assigned to specific team members versus the total servers available in the team
    Affected if Multiple team members have access to different subsets of servers, and any member can reach terminal endpoints for servers outside their assigned scope
  4. Test cross-server terminal access
    As a low-privilege team member, attempt to establish a terminal websocket connection to a server to which that user should not have access according to team permissions
    Affected if The connection succeeds and provides shell access to a server the user was not authorized to access
  5. Inspect terminal authorization middleware
    Review the Coolify source code or API configuration for the terminal websocket bootstrap routes to confirm whether authorization middleware is present and enforced on those endpoints
    Affected if The terminal websocket routes lack proper authorization checks that validate user-server permissions before granting terminal access

A user is affected if running Coolify version prior to 4.0.0-beta.471 and the terminal websocket feature is accessible to team members who should not have terminal access to certain servers.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Coolify to version 4.0.0-beta.471 or later to implement proper terminal authorization checks. If immediate upgrade is not feasible, consider restricting websocket terminal access at the network layer or temporarily disabling terminal functionality for low-privileged team members.

Recommended fix High confidence

4.0.0-beta.471

  1. Check current Coolify version using the Coolify CLI or web interface
  2. Upgrade Coolify to version 4.0.0-beta.471 or later
  3. After upgrade, verify that terminal websocket routes now enforce proper authorization
  4. Confirm low-privileged team members can no longer access terminal routes for servers outside their authorized scope

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
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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