Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-62347medium5.9

Element Call exposes shared passwords in logs

Impact

Element Call, a Matrix video conferencing app, logs the password URL query parameter in versions 0.16.0 to 0.20.3, potentially disclosing shared passwords when error reports are submitted. This may compromise call confidentiality. Upgrading to version 0.20.3 or later fixes the issue, but does not remove previously collected secrets.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.
Applies when

Upgrading does not remove secrets from previously collected rageshakes, which require separate cleanup by the log-server operator.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

element-hq · GitHub_M

element-call

1 range

Compare with this publisher’s ranges. This does not inspect your installation.

affected

>= 0.16.0, < 0.20.3

unaffected

unknown

Other versions: unknown

Original source description

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.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-62347

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-532 ↗

CWE-532: Insertion of Sensitive Information into Log File

GitHub_M

Related →
Contributing organizations · 1
GitHub_M

Assigning organization

2026-10-30

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

5 sources