CVE-2026-34050
Deferred Deferred - Pending Action

Settings Updates Access in Coolify Prior to 4.0.0-beta.471

Vulnerability report for CVE-2026-34050, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-06

Last updated on: 2026-07-07

Assigner: GitHub, Inc.

Description

Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.471, the Settings/Updates Livewire component does not check isInstanceAdmin in its mount method, allowing non-admin users to access the Updates settings page and potentially modify auto-update settings or trigger update checks. This issue is fixed in version 4.0.0-beta.471.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-06
Last Modified
2026-07-07
Generated
2026-07-27
AI Q&A
2026-07-07
EPSS Evaluated
2026-07-25
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
coolify coolify to 4.0.0-beta.471 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The vulnerability exists in Coolify, an open-source tool for managing servers, applications, and databases. Before version 4.0.0-beta.471, the Settings/Updates Livewire component did not verify if a user was an instance administrator in its mount method. This flaw allowed non-admin users to access the Updates settings page, where they could potentially change auto-update settings or trigger update checks.

Detection Guidance

This vulnerability involves unauthorized access to the Settings/Updates Livewire component in Coolify versions prior to 4.0.0-beta.471 by non-admin users. Detection can focus on identifying unauthorized access attempts to the Updates settings page or modification of auto-update settings by users without admin privileges.

Since the issue is related to missing authorization checks in the mount() method of the Updates component, you can detect it by checking the version of Coolify running on your system. Versions before 4.0.0-beta.471 are vulnerable.

To detect unauthorized access attempts, you can monitor web server logs or application logs for requests to the Updates settings page by users who are not instance admins.

Suggested commands to check the installed Coolify version and search logs for suspicious access:

  • Check Coolify version (assuming Coolify is installed via Docker): docker exec -it <coolify_container_name> coolify --version
  • Search web server or application logs for access to the Updates settings page: grep '/settings/updates' /var/log/nginx/access.log
  • Check for non-admin user access attempts (assuming user roles are logged): grep 'non-admin' /path/to/coolify/application/logs/*.log | grep '/settings/updates'

If you find access to the Updates settings page by non-admin users or are running a vulnerable version, it is recommended to upgrade to version 4.0.0-beta.471 or later where the isInstanceAdmin() check is enforced.

Impact Analysis

This vulnerability can impact you by allowing non-administrative users to modify update settings or initiate update checks without proper authorization. This could lead to unauthorized changes in the update process, potentially compromising the integrity or stability of your system.

Compliance Impact

This vulnerability allows non-admin users to access and modify update settings or trigger update checks in Coolify prior to version 4.0.0-beta.471. While it does not directly impact confidentiality, it can affect the integrity of the system by allowing unauthorized changes to update configurations.

Such unauthorized modifications could potentially lead to the deployment of unapproved or vulnerable updates, which might indirectly affect compliance with standards like GDPR or HIPAA that require maintaining system integrity and security controls.

However, there is no explicit information provided about direct impacts on data privacy or regulatory compliance in the available context.

Mitigation Strategies

To mitigate this vulnerability, upgrade Coolify to version 4.0.0-beta.471 or later, where the issue has been fixed.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-34050. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart