Element Call reports full URLs of visited pages to analytics serverGHSA-6vhh-4xw6-h2h2
GHSA-6vhh-4xw6-h2h2 is a Information Exposure vulnerability in @element-hq/element-call-embedded. A fix is available for @element-hq/element-call-embedded — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-6vhh-4xw6-h2h2.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@element-hq/element-call-embeddednpmDescription
Impact
Element Call versions 0.5.17 through 0.19.3 report analytics data to a PostHog server, when configured to by a posthog key in config.json or by the posthogApiHost and posthogApiKey URL parameters. Several fields of this data ($initial_person_info, $session_entry_url, and $current_url) were found to contain the full URL of the user's visited page, including the fragment.
Users of a standalone Element Call ‘SPA’ instance such as https://call.element.io may therefore have reported the full URLs of certain calls, including encryption passwords, to the configured PostHog server, potentially compromising the confidentiality of the calls to actors who could access both the PostHog analytics data and the encrypted media streams.
The same issue is present in Element Call's embedded package, but in practice it does not impact applications using this package (including Element Web, Element Desktop, Element X iOS, and Element X Android) because they distribute encryption keys over Matrix rather than encoding a password in the URL.
Patches
Patched in Element Call 0.19.4.
Workarounds
Users may opt out of analytics in the 'Feedback' tab of Element Call's settings and create new links for future calls.
Admins who host Element Call as a standalone application may disable PostHog analytics entirely by removing the posthog key from their deployment's config.json file.
For more information
If there are any questions or comments about this advisory, please send an email to security at element.io.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @element-hq/element-call-embedded | ≥ 0.5.17&&< 0.19.4 | 0.19.4npm install @element-hq/element-call-embedded@0.19.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @element-hq/element-call-embedded, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @element-hq/element-call-embedded to 0.19.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6vhh-4xw6-h2h2 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is GHSA-6vhh-4xw6-h2h2 in your dependencies?
Find it across npm, including transitive dependencies.