# CVE-2026-121587: Coolify before 4.1.1 Application Name Enumeration via Manual Webhook Endpoints


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 7 Nov 2026
- **Also known as:** GHSA-3r7m-vx77-m833

## What is CVE-2026-121587?

CVE-2026-121587 is a medium-severity vulnerability in coollabsio coolify, published on 3 Nov 2026. 

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-121587?


## How do I fix CVE-2026-121587?

No fix has been published for CVE-2026-121587 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121587 being exploited?

There is no known exploitation of CVE-2026-121587 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121587 and fix it if it is affected.

What it is: CVE-2026-121587 is a medium-severity vulnerability in coollabsio coolify, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121587 in the wild and no public exploit code.

Affected product: coollabsio coolify. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121587/ (Markdown: https://insights.sbomify.com/CVE-2026-121587/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121587
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121587
- OSV: https://osv.dev/vulnerability/CVE-2026-121587

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121587/
Summaries are generated and may contain mistakes; the official description above is the record.
