CVE-2026-41896

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

Unauthenticated Deployment Trigger via Webhook HMAC Bypass with Null Secret · Advisory · coollabsio/coolify · GitHub

https://github.com/coollabsio/coolify/security/advisories/GHSA-w8wm-r924-f65v

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 140 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 40 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-10-12 15:44 UTCEG score recompute
  5. 2026-10-11 19:49 UTCEG score recompute
  6. 2026-10-11 17:04 UTCEG score recompute
  7. 2026-10-11 14:30 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  19. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  20. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  21. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-09-23 07:26 UTCEG score recompute
  23. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  25. 2026-09-18 06:56 UTCEG score recompute
Show 75 more
  1. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  4. 2026-09-14 00:50 UTCEG score recompute
  5. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  6. 2026-09-12 15:13 UTCEG score recompute
  7. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  8. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  9. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  10. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  11. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  13. 2026-09-06 14:39 UTCEG score recompute
  14. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  17. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-08-30 18:24 UTCEG score recompute
  21. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-08-27 22:45 UTCEG score recompute
  24. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  26. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  27. 2026-08-25 01:10 UTCEG score recompute
  28. 2026-08-24 12:39 UTCEG score recompute
  29. 2026-08-23 10:26 UTCEG score recompute
  30. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  31. 2026-08-22 08:45 UTCEG score recompute
  32. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  33. 2026-08-21 06:44 UTCEG score recompute
  34. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-08-20 05:41 UTCEG score recompute
  36. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-08-18 23:09 UTCEG score recompute
  38. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-08-18 06:29 UTCEG score recompute
  40. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-08-16 21:44 UTCEG score recompute
  42. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-08-16 09:13 UTCEG score recompute
  44. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-08-15 08:11 UTCEG score recompute
  46. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  47. 2026-08-14 06:47 UTCEG score recompute
  48. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  49. 2026-08-12 15:40 UTCEG score recompute
  50. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-08-11 14:36 UTCEG score recompute
  52. 2026-08-11 13:43 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  53. 2026-08-11 02:04 UTCEG score recompute
  54. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  55. 2026-08-10 00:50 UTCEG score recompute
  56. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  57. 2026-08-08 23:48 UTCEG score recompute
  58. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  59. 2026-08-07 22:44 UTCEG score recompute
  60. 2026-08-06 21:41 UTCEG score recompute
  61. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  62. 2026-08-05 20:39 UTCEG score recompute
  63. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  64. 2026-08-04 16:36 UTCEG score recompute
  65. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  66. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  67. 2026-08-03 15:26 UTCEG score recompute
  68. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  69. 2026-08-02 14:23 UTCEG score recompute
  70. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  71. 2026-08-01 13:21 UTCEG score recompute
  72. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  73. 2026-07-30 23:39 UTCEG score recompute
  74. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  75. 2026-07-30 11:07 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41896?
CVE-2026-41896 is a high-severity vulnerability; its CVE record was published on June 29, 2026. 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 manualwebhooksecretgithub field, which is used by Coolify's webhook endpoints to validate incoming requests, is nullable with no default —…
When was the CVE record for CVE-2026-41896 published?
The CVE record for CVE-2026-41896 was published on June 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 30, 2026; the record at its source may have been updated since.
Is CVE-2026-41896 actively exploited?
CVE-2026-41896 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-41896?
CVE-2026-41896 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-41896?
The CVE record for CVE-2026-41896 names the fix: "This vulnerability is fixed in 4.0.0-beta.474."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-41896

Explore →

Is Your Infrastructure Affected by CVE-2026-41896?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs