Servers and applications
CVE-2026-34048
Missing authorization on terminal websocket bootstrap routes allows low-privileged members to execute commands on team servers
- Severity
- Critical 9.9
- Published
- 2 Jul 2026
- Last changed
- 2 Jul 2026
- Added to UpHeron
- 22 Oct 2026
- Fixed in
- 4.0.0-beta.471
- Exploit chance
- 0.8% in the next 30 daysHigher than 57% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H- Also known as
- GHSA-mw6q-2hmg-mhxv
- Sources
- Project advisories (GitHub)
Description
The terminal feature is intended to be restricted to team administrators/owners, but the websocket bootstrap endpoints only check whether the user is logged in. As a result, an authenticated low-privileged team member can open an admin-only terminal websocket session and execute commands on team servers that are terminal-enabled.
I validated this locally on commit 06f60c9a98bead0c932c6adf7fd43a45d9149048 (v4.0.0-beta.469). Using a non-admin member account, I was able to reach the terminal websocket, receive pty-ready, and execute id, whoami, and hostname on the managed host. In my test lab, the configured server user was root, so the resulting output included uid=0(root) and whoami=root.
At the vulnerable revision:
- GET /terminal is protected by terminal authorization middleware (can.access.terminal)
- POST /terminal/auth only checks auth()->check()
- POST /terminal/auth/ips only checks auth()->check()
This creates an authorization mismatch between the UI and the realtime backend.
Workarounds
The immediate fix is to enforce the same authorization boundary on the websocket bootstrap routes that is already enforced on the terminal UI.
Minimum fix:
- apply can.access.terminal to both POST /terminal/auth and POST /terminal/auth/ips
- ensure low-privileged members receive an authorization failure from both routes
- add regression tests covering:
- unauthenticated users denied
- authenticated non-admin members denied
- authorized admins/owners allowed
Recommended hardening:
Affected software
| Software | Affected versions |
|---|---|
CoolifyServers and applications · github:coollabsio/coolify |
|
About Coolify
An open-source, self-hostable PaaS alternative to Vercel, Heroku & Netlify that lets you easily deploy static sites, databases, full-stack applications and 360+ one-click services on your own servers.
- Docker Hub pulls
- 4,970,195Docker Hub, 15 Nov 2026
- GitHub stars
- 66,095GitHub, 15 Nov 2026
- Forks
- 5,989GitHub, 15 Nov 2026
- Latest release
- v4.7.5GitHub, 15 Nov 2026
- Released
- 10 Nov 2026GitHub
- License
- Apache-2.0GitHub
- First published on GitHub
- 25 Jan 2021GitHub
Source code Website Docker image
Vulnerabilities in Coolify
- In our list
- 74
- Published in the last 12 months
- 62
- Critical, last 12 months
- 12
- High, last 12 months
- 28
- Known exploited
- 0
- CVE-2026-121587Coolify before 4.1.1 Application Name Enumeration via Manual Webhook EndpointsMedium 6.9 3 Nov 2026
- CVE-2026-34037Cross-Tenant Resource Cloning via Broken Object-Level Authorization in cloneTo()Critical 9.9 2 Jul 2026
- CVE-2026-34035Host RCE via Log Drain secret/env command injectionHigh 8.8 2 Jul 2026
- CVE-2026-34034Host RCE via Sentinel token injectionHigh 8.8 2 Jul 2026
- CVE-2026-34044Cross-team IDOR in logs component (resource lookup not team-scoped)High 7.7 2 Jul 2026
- CVE-2026-32718API ability mismatch allows mutation with `read` tokenMedium 6.5 2 Jul 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-34048
- GitHub Advisory Database https://github.com/advisories/GHSA-mw6q-2hmg-mhxv
- github.com https://github.com/coollabsio/coolify/security/advisories/GHSA-mw6q-2hmg-mhxv