npm package report

Is @element-hq/element-call-embedded safe?

1 known vulnerability, worst severity HIGH.

cvss
8.6

how bad it is if exploited, out of 10

epss
0.20%

chance of exploitation in the next 30 days

xyz score
3.3

CyberXYZ composite, out of 10

fig. 01 — GHSA-6vhh-4xw6-h2h2, the advisory selected below

// advisories

GHSA-6vhh-4xw6-h2h2

HIGHCVE-2026-48007

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 ($initialpersoninfo, $sessionentryurl, and $currenturl) were found to contain the full URL of the user's visited page, including the fragment.

Affected
>=0.5.17, <0.19.4, >= 0.5.17, <= 0.19.3
Fixed in
0.19.4
Weakness
CWE-200
Published
2026-06-11
Source
osv

NVDMITREOSV

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 03:45 UTC. The most recent advisory here was published 2026-06-11. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is @element-hq/element-call-embedded safe? npm package security report | CyberXYZ