# CVE-2026-48007: Element Call reports full URLs of visited pages to analytics server

> Element Call leaks full URLs including encryption passwords to analytics servers, compromising call confidentiality for standalone instances.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-6vhh-4xw6-h2h2

## What is CVE-2026-48007?

CVE-2026-48007 is a high-severity vulnerability in element-hq element-call, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Element Call is a native Matrix video conferencing application. 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. The issue is patched in Element Call 0.19.4. Some workarounds are available. 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-48007?

2 open source packages ship an affected version, including @element-hq/element-call-embedded.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@element-hq/element-call-embedded` | npm | From 0.5.17 | 0.19.4 |
| `@element-hq/element-call-embedded` | npm | From 0.5.17 | 0.19.4 |

## How do I fix CVE-2026-48007?

Upgrade @element-hq/element-call-embedded to 0.19.4 or later.

## Is CVE-2026-48007 being exploited?

There is no known exploitation of CVE-2026-48007 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48007 and fix it if it is affected.

What it is: CVE-2026-48007 is a high-severity vulnerability in element-hq element-call, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48007 in the wild and no public exploit code.

Affected packages and fixed versions:
- @element-hq/element-call-embedded (npm): affected from 0.5.17; fixed in 0.19.4
- @element-hq/element-call-embedded (npm): affected from 0.5.17; fixed in 0.19.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48007/ (Markdown: https://insights.sbomify.com/CVE-2026-48007/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48007
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48007
- OSV: https://osv.dev/vulnerability/CVE-2026-48007

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48007/
Summaries are generated and may contain mistakes; the official description above is the record.