Servers and applications
CVE-2026-41896
Unauthenticated Deployment Trigger via Webhook HMAC Bypass with Null Secret
- Severity
- High 7.5
- Published
- 25 Jun 2026
- Last changed
- 25 Jun 2026
- Added to UpHeron
- 22 Oct 2026
- Fixed in
- 4.0.0-beta.474
- Exploit chance
- 0.3% in the next 30 daysHigher than 20% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Change data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N- Also known as
- GHSA-w8wm-r924-f65v
- Sources
- Project advisories (GitHub)
Description
Coolify's webhook endpoints validate incoming requests using HMAC-SHA256 signatures. The HMAC key is the application's manual_webhook_secret_github field, which is nullable with no default — meaning newly created applications have a null webhook secret.
Here's the problem: PHP's hash_hmac() function silently coerces a null key to an empty string ''. So when the secret is null, the server computes hash_hmac('sha256', $payload, '') — a deterministic value that any attacker can calculate independently. By sending X-Hub-Signature-256: sha256=, an unauthenticated attacker can forge a valid signature and trigger deployments.
This affects all three webhook controllers (GitHub, Bitbucket, Gitea). The GitHub path is the most common since Coolify primarily integrates with GitHub repositories.
The default configuration is vulnerable — a user must explicitly navigate to the application settings and set a webhook secret to be protected.
Affected software
| Software | Affected versions |
|---|---|
CoolifyServers and applications · github:coollabsio/coolify |
|
About Coolify
An open-source, self-hostable PaaS alternative to Vercel, Heroku & Netlify that lets you easily deploy static sites, databases, full-stack applications and 360+ one-click services on your own servers.
- Docker Hub pulls
- 4,970,195Docker Hub, 15 Nov 2026
- GitHub stars
- 66,095GitHub, 15 Nov 2026
- Forks
- 5,989GitHub, 15 Nov 2026
- Latest release
- v4.7.5GitHub, 15 Nov 2026
- Released
- 10 Nov 2026GitHub
- License
- Apache-2.0GitHub
- First published on GitHub
- 25 Jan 2021GitHub
Source code Website Docker image
Vulnerabilities in Coolify
- In our list
- 74
- Published in the last 12 months
- 62
- Critical, last 12 months
- 12
- High, last 12 months
- 28
- Known exploited
- 0
- CVE-2026-121587Coolify before 4.1.1 Application Name Enumeration via Manual Webhook EndpointsMedium 6.9 3 Nov 2026
- CVE-2026-34037Cross-Tenant Resource Cloning via Broken Object-Level Authorization in cloneTo()Critical 9.9 2 Jul 2026
- CVE-2026-34035Host RCE via Log Drain secret/env command injectionHigh 8.8 2 Jul 2026
- CVE-2026-34034Host RCE via Sentinel token injectionHigh 8.8 2 Jul 2026
- CVE-2026-34044Cross-team IDOR in logs component (resource lookup not team-scoped)High 7.7 2 Jul 2026
- CVE-2026-32718API ability mismatch allows mutation with `read` tokenMedium 6.5 2 Jul 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-41896
- GitHub Advisory Database https://github.com/advisories/GHSA-w8wm-r924-f65v
- github.com https://github.com/coollabsio/coolify/security/advisories/GHSA-w8wm-r924-f65v