Skip to main content
VulnerabilityPublished

CVE-2026-24044: element-hq ess-helm · PRNG

Affects element-hq ess-helmSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.2 Critical : upgrade to 25.12.1 as a priority.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 4.0 base score
9.2Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 25.12.1, 0.5.7
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade ess-helm to 25.12.1; matrix-tools to 0.5.7.

Affected software

ProductAffectedFixed in
element-hqess-helmAffected
  • <25.12.1
Fixed in
  • 25.12.1
element-hqmatrix-toolsAffected
  • <0.5.7
Fixed in
  • 0.5.7

AI-suggested

European organizations should immediately upgrade their ESS Community Helm Chart deployments to version 25.12.1 or later, which includes matrix-tools 0.5.7 with the secure key generation fix. Administrators should verify that initSecrets.enabled is not set to false and that synapse.signingKey is explicitly defined to avoid fallback to insecure key generation. Additionally, organizations should audit existing server keys for potential compromise and consider rotating keys post-upgrade. Network segmentation and strict access controls should be enforced to limit exposure of Matrix servers to untrusted networks. Monitoring for anomalous server behavior or unexpected event injections can help detect exploitation attempts. Finally, organizations should maintain up-to-date backups of room states and configurations to enable recovery in case of disruption.

Description

Element Server Suite Community Edition (ESS Community) deploys a Matrix stack using the provided Helm charts and Kubernetes distribution. The ESS Community Helm Chart secrets initialization hook (using matrix-tools container before 0.5.7) is using an insecure Matrix server key generation method, allowing network attackers to potentially recreate the same key pair, allowing them to impersonate the victim server. The secret is generated by the secrets initialization hook, in the ESS Community Helm Chart values, if both initSecrets.enabled is not set to false and synapse.signingKey is not defined. Given a server key in Matrix authenticates both requests originating from and events constructed on a given server, this potentially impacts confidentiality, integrity and availability of rooms which have a vulnerable server present as a member. The confidentiality of past conversations in end-to-end encrypted rooms is not impacted. The key generation issue was fixed in matrix-tools 0.5.7, released as part of ESS Community Helm Chart 25.12.1.

References

Community reviews

Loading reviews…