---
id: "CVE-2026-62347"
kind: "vulnerability"
aliases: ["CVE-2026-62347"]
title: "Element Call: password query parameter leaks into shared bug report logs"
severity: "medium"
cvss: 5.9
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["element-call", "matrix", "package", "self-hosted"]
not_affected_if: ["no-rageshake-submission", "version-0.20.3-or-later"]
published_at: "2026-10-30T22:16:56+00:00"
first_seen_at: "2026-10-30T22:25:56+00:00"
updated_at: "2026-10-30T22:27:19+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-62347", "first_seen_at": "2026-10-30T22:25:56+00:00"}]
---

# Element Call: password query parameter leaks into shared bug report logs

Element Call versions 0.16.0 through 0.20.3 log the shared call password from the URL query string. When a user submits a rageshake error report, those logs go to the application operator, exposing the password used to encrypt the call.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the deployed Element Call version against `0.20.3`.
- Review whether users submit rageshake bug reports or debug logs from Element Call.

## Fix

- Upgrade Element Call to `0.20.3`.
- Previously collected rageshakes need separate cleanup by the log-server operator; upgrading does not remove them.

## Timeline

- 2026-10-30T22:25:56+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-62347

## From the sources

Element Call is a native Matrix video conferencing application. From 0.16.0 until 0.20.3, the standalone Element Call `SPA` logs the `password` URL query parameter. When a user submits an error report, called a rageshake, these logs are shared with the application operator. Users can therefore unintentionally disclose the shared `password` used to encrypt the call, potentially compromising call confidentiality. Avoiding submission of bug reports or debug logs prevents this disclosure path in affected versions. Upgrading does not remove secrets from previously collected `rageshakes`, which require separate cleanup by the log-server operator. This issue is fixed in version 0.20.3.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_