{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 0.19.3"
      },
      "package": {
        "ecosystem": "npm",
        "name": "@element-hq/element-call-embedded"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.5.17"
            },
            {
              "fixed": "0.19.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-48007"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-200"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-06-11T13:26:17Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Impact\n\nElement 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\u0027s visited page, including the fragment.\n\nUsers of a standalone Element Call \u2018SPA\u2019 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.\n\nThe same issue is present in Element Call\u0027s 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.\n\n### Patches\n\nPatched in Element Call 0.19.4.\n\n### Workarounds\n\nUsers may opt out of analytics in the \u0027Feedback\u0027 tab of Element Call\u0027s settings and create new links for future calls.\n\nAdmins who host Element Call as a standalone application may disable PostHog analytics entirely by removing the `posthog` key from their deployment\u0027s config.json file.\n\n### For more information\n\nIf there are any questions or comments about this advisory, please send an email to [security at element.io](mailto:security@element.io).",
  "id": "GHSA-6vhh-4xw6-h2h2",
  "modified": "2026-06-11T13:26:17Z",
  "published": "2026-06-11T13:26:17Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/element-hq/element-call/security/advisories/GHSA-6vhh-4xw6-h2h2"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/element-hq/element-call"
    },
    {
      "type": "WEB",
      "url": "https://github.com/element-hq/element-call/releases/tag/v0.19.4"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "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",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Element Call reports full URLs of visited pages to analytics server"
}