CVE-2026-27956
Received Received - Intake

Domain Enumeration in Coolify via Query Parameter

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

Publication date: 2026-06-30

Last updated on: 2026-06-30

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.464, `GET /api/v1/servers/{server_uuid}/domains?uuid={app_uuid}` bypasses team scoping when the optional uuid query parameter is provided. Any authenticated API user can enumerate domain names (FQDNs) of applications belonging to other teams. This vulnerability is fixed in 4.0.0-beta.464.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-06-30
Last Modified
2026-06-30
Generated
2026-06-30
AI Q&A
2026-06-30
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

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

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-27956 is a vulnerability in Coolify versions up to 4.0.0-beta.406 that allows authenticated API users to bypass team scoping and enumerate domain names (FQDNs) of applications belonging to other teams.

This happens in the `GET /api/v1/servers/{server_uuid}/domains?uuid={app_uuid}` endpoint when the optional uuid query parameter is provided. The endpoint performs a global query that does not filter by team, allowing unauthorized access to internal domain names, application structures, and deployment details.

The root cause is an authorization bypass through user-controlled key, classified as CWE-639.

Impact Analysis

This vulnerability allows any authenticated API user to access domain names and related application information of other teams without proper authorization.

Such unauthorized information disclosure can lead to exposure of internal infrastructure details, which could be leveraged for further attacks or reconnaissance.

Although the CVSS score is moderate (4.3), the impact includes confidentiality loss of internal domain and application data.

Detection Guidance

This vulnerability can be detected by attempting to access the vulnerable API endpoint with an authenticated user and observing if domain names of applications belonging to other teams are returned.

Specifically, sending a GET request to the endpoint `/api/v1/servers/{server_uuid}/domains?uuid={app_uuid}` with valid authentication and checking if domain names from other teams are enumerated indicates the presence of the vulnerability.

A sample command using curl to test this could be:

  • curl -H "Authorization: Bearer <token>" "https://<coolify-server>/api/v1/servers/<server_uuid>/domains?uuid=<app_uuid>"

If the response includes domain names from applications not belonging to the authenticated user's team, the vulnerability exists.

Mitigation Strategies

The immediate mitigation step is to upgrade Coolify to version 4.0.0-beta.464 or later, where the vulnerability is fixed.

The fix involves adding proper team scoping to the `uuid` parameter path or modifying the `getDomainsByUuid()` function to accept and enforce team ID filtering.

Until the upgrade can be performed, restrict access to the vulnerable API endpoint to trusted users only and monitor API usage for suspicious enumeration attempts.

Compliance Impact

This vulnerability allows authenticated API users to enumerate domain names of applications belonging to other teams by bypassing team scoping. This unauthorized access to internal domain names and application details could lead to exposure of sensitive information.

Such unauthorized information disclosure may impact compliance with standards and regulations like GDPR and HIPAA, which require strict controls on access to sensitive data and protection of personal or confidential information.

However, the provided information does not explicitly state the direct impact on compliance with these regulations.

Chat Assistant

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

EPSS Chart