Live › vulnerability › CVE-2026-121587
Coolify before 4.1.1 has manual GitHub, GitLab, Bitbucket and Gitea webhook endpoints that accept a wildcard repository name before signature checks. An unauthenticated attacker can list the names of applications belonging to every team on the instance.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 17:21 UTC. All times on this page are UTC.
Teams that self-host Coolify before 4.1.1 and expose its webhook endpoints to the internet are exposed. The flaw is an information leak of application names only; the sources do not say whether code or secrets are reachable. Instances on managed hosting or on a private network that blocks webhook traffic can skip it.
No product ranges from the sources yet.
coolify --version or the version shown in the Coolify dashboard, and compare it with 4.1.1.4.1.1 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Coolify before 4.1.1 contains an information disclosure vulnerability that allows unauthenticated attackers to enumerate application names across all teams via manual GitHub, GitLab, Bitbucket and Gitea webhooks. Attackers can send a repository name of % or empty with a common branch like main, exploiting unescaped LIKE wildcards to receive every matching application name before signature verification.
This page as .md · .json · in your agent: get_signal("CVE-2026-121587")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.