dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-41896

HIGH · 7.5 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to 4.0.0-beta.474, the HMAC key is the application's manual_webhook_secret_github field, which is used by Coolify's webhook endpoints to validate incoming requests, is nullable with no default — meaning newly created applications have a null webhook secret. 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=<hash_hmac('sha256', payload, '')>, an unauthenticated attacker can forge a valid signature and trigger deployments. This vulnerability is fixed in 4.0.0-beta.474.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Coolify's webhook signature validation uses a nullable manual_webhook_secret_github field that defaults to null for new applications. PHP's hash_hmac() coerces null to an empty string '', producing a deterministic HMAC that attackers can independently calculate. By forging this signature, unauthenticated attackers can trigger arbitrary deployments.

MitigationUpgrade to Coolify 4.0.0-beta.474 or later, and proactively configure non-null webhook secrets for all existing applications to prevent exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Coolify version
    Check the Coolify instance version through the admin UI, API endpoint, or container/tag version. Compare this version to 4.0.0-beta.474.
    Affected if Running a version earlier than 4.0.0-beta.474
  2. Examine manual_webhook_secret_github field
    Query the Coolify database or inspect application configurations to find the value of the manual_webhook_secret_github field for existing applications.
    Affected if Any application has a null or empty string value for manual_webhook_secret_github
  3. Confirm webhook endpoint exposure
    Verify that the Coolify webhook endpoint is accessible from untrusted networks (typically at /webhooks/deploy/{id}).
    Affected if Webhook endpoint is publicly accessible without additional authentication layers

The environment is affected if running Coolify versions before 4.0.0-beta.474 with any application configured with a null or empty manual_webhook_secret_github field, allowing unauthenticated attackers to forge HMAC signatures.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Coolify 4.0.0-beta.474 or later, and proactively configure non-null webhook secrets for all existing applications to prevent exploitation.

Recommended fix High confidence

4.0.0-beta.474

  1. Upgrade Coolify to version 4.0.0-beta.474 or later to obtain the security fix
  2. After upgrading, verify that the manual_webhook_secret_github field is properly configured for all applications
  3. Ensure that webhook secrets are set to non-null, non-empty values to maintain proper HMAC validation
  4. Test webhook endpoints to confirm signature validation works correctly with the new implementation
Caveat Beta releases may contain additional changes; test thoroughly in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41896 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41896 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data