Skip to main content
VulnerabilityPublished

CVE-2026-62347: element-call · Sensitive Data in Logs

Affects element-callSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 0.20.3 when convenient.

Data as of 30 Oct 2026, 21:52 UTC

CVSS 4.0 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.05.9
Patch
Available – fixed in 0.20.3
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 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 30 Oct 2026.

What to do

Upgrade element-call to 0.20.3.

Affected software

ProductAffectedFixed in
element-hqelement-callAffected
  • >=0.16.0 <0.20.3
Fixed in
  • 0.20.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Element Call to version 0.20.3 or later to prevent logging of the password parameter in error reports. Avoid submitting bug reports or debug logs containing sensitive information in affected versions. For previously collected logs, perform manual cleanup to remove sensitive password data.

Description

Element Call versions from 0.16.0 up to but not including 0.20.3 log the password URL query parameter in error reports (rageshakes). These logs are shared with the application operator, potentially exposing the encryption password and compromising call confidentiality. The issue is fixed in version 0.20.3. Upgrading prevents future disclosures but does not remove secrets from previously collected logs, which require manual cleanup.

References

Community reviews

Loading reviews…