Insufficient Authorization in Coolify Prior to 4.0.0-beta.466

Publication date: 2026-07-06

Last updated on: 2026-07-06

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.466, mutating API validation endpoints are guarded by read ability, allowing read-scoped API tokens to perform state-changing operations such as validating cloud tokens and servers. This issue is fixed in version 4.0.0-beta.466.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-06

Last Modified

2026-07-06

Generated

2026-07-07

AI Q&A

2026-07-07

EPSS Evaluated

N/A

NVD

CVE-2026-32718

Affected Vendors & Products

Vendor	Product	Version / Range
coolify	coolify	to 4.0.0-beta.466 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-863	The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

Mitigation Strategies

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

Executive Summary

The vulnerability in Coolify versions prior to 4.0.0-beta.466 involves the mutating API validation endpoints being protected only by read permissions. This means that API tokens with read-only scope can perform state-changing operations, such as validating cloud tokens and servers, which should normally require higher privileges.

Impact Analysis

This vulnerability allows attackers or users with read-scoped API tokens to perform unauthorized state-changing actions. This can lead to unauthorized validation of cloud tokens and servers, potentially compromising the integrity of your server and application management processes.

Hi! I’m here to help you understand CVE-2026-32718. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70