Quick answers
- Is CVE-2026-62347 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62347 being exploited in the wild.
- How severe is CVE-2026-62347?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Element Call 0.16.0 to 0.20.2.
- Is there a fix for CVE-2026-62347?
- Yes: fixed in 0.20.3. Until then: Avoid submitting error reports or debug logs in affected versions. Note that upgrading does not retroactively remove secrets from previously collected rageshakes, which require separate cleanup by the log-server operator. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62347 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-62347?
- Check whether you run Element Call at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.20.3
Avoid submitting error reports or debug logs in affected versions. Note that upgrading does not retroactively remove secrets from previously collected rageshakes, which require separate cleanup by the log-server operator.
Technical details
The standalone Element Call SPA unintentionally logs the password URL query parameter during normal operation. When users submit rageshakes (debug reports), the logs are bundled and transmitted to the operator, inadvertently disclosing the call encryption password. This is a logging/information disclosure issue affecting versions 0.16.0 through 0.20.2, fixed by redacting the password parameter from logs.
Affected products
- Element Call 0.16.0 to 0.20.2
Timeline
- 2026-10-30: disclosed