CVE-2026-48007

HIGHPre-NVD 8.68.6—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.6
EG Score
8.6(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity86% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

June 11, 2026

Last Modified

August 10, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
Patch available. Sources: github_release, github.
github_release Patch Available

v0.19.4

Patch available: element-hq/element-call v0.19.4

https://github.com/element-hq/element-call/releases/tag/v0.19.4
github Patch Available

Element Call reports full URLs of visited pages to analytics server · Advisory · element-hq/element-call · GitHub

https://github.com/element-hq/element-call/security/advisories/GHSA-6vhh-4xw6-h2h2

Vendor Advisories for CVE-2026-48007(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@element-hq/element-call-embedded—0.19.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-25 00:05 UTCEG score recompute
  4. 2026-08-23 10:43 UTCEG score recompute
  5. 2026-08-21 23:49 UTCEPSS rescore
  6. 2026-08-21 06:42 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 08:51 UTCEG score recompute
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 14:54 UTCEG score recompute
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 23:07 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 10:45 UTCEG score recompute
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 10:46 UTCEG score recompute
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-13 22:14 UTCEG score recompute
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-12 21:14 UTCEG score recompute
  22. 2026-08-12 13:51 UTCEPSS rescore
  23. 2026-08-11 23:17 UTCEG score recompute
  24. 2026-08-11 01:26 UTCEG score recompute
  25. 2026-08-11 00:00 UTCEPSS rescore
Show 16 more
  1. 2026-08-10 14:31 UTCEG score recompute
  2. 2026-08-10 13:37 UTCEG score recompute
  3. 2026-08-09 16:10 UTCEG score recompute
  4. 2026-08-09 13:46 UTCEPSS rescore
  5. 2026-08-08 18:20 UTCEG score recompute
  6. 2026-08-08 16:37 UTCEPSS rescore
  7. 2026-08-07 20:30 UTCEG score recompute
  8. 2026-08-07 19:37 UTCEG score recompute▲ 8.60
  9. 2026-08-07 19:37 UTCMITRE cvelistV5CVSS v3 → 8.6 · CVSS v4 → 8.6
  10. 2026-07-30 09:41 UTCEG score recompute
  11. 2026-07-26 20:54 UTCEG score recompute
  12. 2026-07-23 03:18 UTCEG score recompute
  13. 2026-06-14 23:18 UTCEPSS rescore
  14. 2026-06-13 23:00 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-11 13:56 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48007?
CVE-2026-48007 is a high vulnerability published on June 11, 2026. 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 ($initialpersoninfo,…
When was CVE-2026-48007 disclosed?
CVE-2026-48007 was first published in the National Vulnerability Database on June 11, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48007 actively exploited?
CVE-2026-48007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.1% of all scored CVEs.
What is the CVSS score of CVE-2026-48007?
CVE-2026-48007 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-48007?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48007, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-48007

Explore →

Is Your Infrastructure Affected by CVE-2026-48007?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs