Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-41896Published 2026-06-29

CVE-2026-41896 — coollabsio coolify

high

As of 2026-06-30, CVE-2026-41896 is a HIGH-severity vulnerability in coollabsio coolify, CVSS v3.1 7.5, EPSS 0.2% (13.8th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-41896 as of 2026-06-30; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v3.1
7.5/10High
EPSS
0.2%Higher than 13.8% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
4.3/10Threadlinqs triage score
Published
Updated 2026-06-30
CVSS v3.1 7.5 (HIGH) · EPSS 0.2% (higher than 13.8% of all scored CVEs) · Priority 4.3/10 · Published 2026-06-29

Last updated:

What is CVE-2026-41896?

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=, an unauthenticated attacker can forge a valid signature and trigger deployments. This vulnerability is fixed in 4.0.0-beta.474.

The record classifies CVE-2026-41896 under weakness class CWE-287. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs no user interaction, and has high impact on integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 98 days ago.

Severity and exploitation probability

CVSS v3.1 base score
7.5 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS (FIRST)
0.2% probability of exploitation in the next 30 days, higher than 13.8% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
4.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-06-29, last modified 2026-06-30

Is CVE-2026-41896 being exploited?

It currently carries a trending score of 33 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-41896

No vendor patch reference has been recorded for CVE-2026-41896 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-41896

No threat campaign in the Threadlinqs corpus currently references CVE-2026-41896, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch