# CVE-2026-121587: Coolify information disclosure via webhook enumeration

Source: https://junglewise.ai/threats/cve-2026-121587-coolify-before-4-1-1-contains-an-information-disclosure  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-121587 · Severity: medium · CVSS 5.3 · Published 2026-11-03

Coolify is a self-hosted platform-as-a-service alternative for deploying applications. Versions before 4.1.1 allow unauthenticated attackers to enumerate application names across all teams by sending specially crafted webhook requests. An attacker can discover sensitive application naming information without authentication, potentially revealing proprietary system architecture or enabling targeted attacks.

Technologies: [Coollabs Coolify](https://junglewise.ai/threats/technologies/coolify). Vendors: [Coollabs](https://junglewise.ai/threats/vendors/coollabs).

## Quick answers

**Is CVE-2026-121587 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-121587 being exploited in the wild.

**How severe is CVE-2026-121587?** Medium severity, with a CVSS score of 5.3, published 3 November 2026.

**Which products and versions are affected?** Coollabs Coolify before 4.1.1.

**Is there a fix for CVE-2026-121587?** Yes: fixed in 4.1.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-121587 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-121587?** Check whether you run Coollabs Coolify at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 4.1.1

## Technical details

The vulnerability exists in webhook handlers (GitHub, GitLab, Bitbucket, Gitea) that perform database queries using unescaped LIKE wildcards before verifying webhook signatures. An attacker can send repository names containing SQL wildcard characters (%) or empty values with a common branch name to enumerate all matching application names. The attack is network-accessible and requires no authentication or user interaction.

## Affected products

- coollabs Coolify before 4.1.1

## Timeline

- 2026-11-03: disclosed
- 2026-11-03: advisory

## References

- [https://github.com/coollabsio/coolify](https://github.com/coollabsio/coolify)
- [https://github.com/coollabsio/coolify/blob/v4.1.0/app/Http/Controllers/Webhook/Github.php](https://github.com/coollabsio/coolify/blob/v4.1.0/app/Http/Controllers/Webhook/Github.php)

## Related threats

- [Coollabsio Coolify path traversal in PostgreSQL init scripts](https://junglewise.ai/threats/cve-2026-42200-coollabsio-coolify-path-traversal-in-postgresql-init-scripts)
- [Coollabs Coolify insufficient session expiration for API tokens](https://junglewise.ai/threats/cve-2026-42172-coollabs-coolify-insufficient-session-expiration-for-api-tokens)
- [Coollabsio Coolify SSRF in S3 storage endpoint validation](https://junglewise.ai/threats/cve-2026-42147-coollabsio-coolify-ssrf-in-s3-storage-endpoint-validation)
- [Coolify account takeover via CSRF in invitation endpoint](https://junglewise.ai/threats/cve-2026-34171-coolify-account-takeover-via-csrf-in-invitation-endpoint)
- [Coollabs Coolify OS command injection in LocalPersistentVolume name](https://junglewise.ai/threats/cve-2026-34168-coollabs-coolify-os-command-injection-in-localpersistentvolume)