CVE-2026-34047
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 · uneditedCoolify 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 did not enforce the expected authorization middleware, allowing an authenticated user to access terminal functionality for resources outside the authorized scope and potentially execute commands. 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 · moderate confidenceCoolify prior to 4.0.0-beta.471 has an authorization bypass in terminal WebSocket bootstrap routes. The routes failed to enforce expected authorization middleware, allowing authenticated users to access terminal functionality for resources outside their authorized scope and potentially execute arbitrary commands.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Coolify installation and versionRun 'coolify --version' from the command line, or check the Coolify dashboard UI for the version number typically displayed in the footer or settings pageAffected if The installed version is below 4.0.0-beta.471 (e.g., 4.0.0-beta.450, 4.0.0-beta.300, 3.x.x)
-
Verify terminal WebSocket endpoint is accessibleCheck if WebSocket routes for terminal functionality are exposed by reviewing the Coolify API endpoints or examining the application's route configuration for paths matching '/terminal' or '/ws/terminal' patternsAffected if Terminal WebSocket routes exist and are reachable without additional authorization enforcement beyond basic authentication
-
Confirm authenticated user access to terminal featuresLog into Coolify as a standard authenticated user and attempt to access the terminal feature for a resource (such as a deployed application or database) that the user does not have explicit permissions to manageAffected if An authenticated user can access terminal functionality for resources outside their defined authorization scope
-
Check for presence of authorization middleware on terminal routesReview Coolify's route definitions or middleware configuration files (typically in the application source under routes/ or bootstrap/ directories) to verify if terminal WebSocket routes explicitly enforce the 'authorization' or 'resource-permission' middlewareAffected if Terminal WebSocket bootstrap routes do not include or fail to execute authorization middleware checks
A Coolify installation is affected if it runs a version prior to 4.0.0-beta.471 and the terminal WebSocket functionality is accessible to authenticated users who should not have access to those terminal resources.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Coolify to version 4.0.0-beta.471 or later to apply the authorization middleware fix.
4.0.0-beta.471
- Identify current Coolify installation version using `coolify --version` or checking the admin panel
- Back up all Coolify data and configurations before upgrading
- Upgrade Coolify to version 4.0.0-beta.471 or later by following the official upgrade instructions at https://coolify.io/docs
- Verify the upgrade was successful by checking the version again
- Test terminal WebSocket functionality to confirm the authorization middleware is now properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34047 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34047 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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