Summary
Element Call reports full URLs of visited pages to analytics server
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.
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.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Patched in Element Call 0.19.4.
Frequently Asked Questions
- What is CVE-2026-48007? CVE-2026-48007 is a high-severity security vulnerability in @element-hq/element-call-embedded (npm), affecting versions >= 0.5.17, <= 0.19.3. It is fixed in 0.19.4.
- Which versions of @element-hq/element-call-embedded are affected by CVE-2026-48007? @element-hq/element-call-embedded (npm) versions >= 0.5.17, <= 0.19.3 is affected.
- Is there a fix for CVE-2026-48007? Yes. CVE-2026-48007 is fixed in 0.19.4. Upgrade to this version or later.
- Is CVE-2026-48007 exploitable, and should I be worried? Whether CVE-2026-48007 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-48007 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-48007? Upgrade
@element-hq/element-call-embeddedto 0.19.4 or later.