Information Disclosure in @element-hq/element-call-embedded (CVE-2026-48007)
Summary
Vulnerability in @element-hq/element-call-embedded (CVE-2026-48007). Risk of unauthorized operations or information disclosure. Exploitable via posthog. Mitigation: upgrade to 0.19.4 or later.
Original description
The description as published by the source.
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,…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48007 has been found in @element-hq/element-call-embedded.
Attackers can target a specific entry point like posthog over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @element-hq/element-call-embedded to 0.19.4 or later.
If unsure, ask your IT team or search "@element-hq/element-call-embedded CVE-2026-48007" on the vendor's site.
CVE-2026-48007 (@element-hq/element-call-embedded) — CWE-200
Attack surface: posthog / posthogApiHost / posthogApiKey
Patched: 0.19.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in @element-hq/element-call-embedded. Attackers reach the vulnerable code path via posthog.
Check the vendor advisory for the affected versions of @element-hq/element-call-embedded. Attack surface: posthog / posthogApiHost / posthogApiKey.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.19.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@element-hq/element-call-embedded' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@element-hq/element-call-embedded' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@element-hq/element-call-embeddedを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @element-hq/element-call-embedded to 0.19.4ステージング環境で 0.19.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web security-advisories@github.com
- web security-advisories@github.com
- web github.com