CVE-2026-92299

HIGHPre-NVD 7.47.4—
EchelonGraph scoreHIGH confidence

Score 7.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-16. a secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

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

@jitsi/electron-sdk before 10.0.5 exposes getDesktopSources() via contextBridge without requiring an active getDisplayMedia() picker, allowing any script in the meeting page to enumerate screens and windows. Attackers can call the jitsi-screen-sharing-get-sources IPC route to retrieve desktop thumbnails at arbitrary resolution without user consent or operating system permission prompts.

CVSS v3
7.4
EG Score
7.4(high)
EG Risk
33(Track)
EG Risk 33/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
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 16, 2026

Advisory Details (6)

Auto-updated Sep 16, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr, github_commit.
generic

@jitsi/electron-sdk before 10.0.5 Unauthorized Screen Capture | Advisories | VulnCheck

https://www.vulncheck.com/advisories/jitsi-electron-sdk-before-10.0.5-unauthorized-screen-capture
generic

GitHub - jitsi/jitsi-meet-electron-sdk: Jitsi Meet SDK for Electron · GitHub

https://github.com/jitsi/jitsi-meet-electron-sdk
generic

jitsi-meet-electron-sdk/screensharing/main.js at v10.0.5 · jitsi/jitsi-meet-electron-sdk · GitHub

https://github.com/jitsi/jitsi-meet-electron-sdk/blob/v10.0.5/screensharing/main.js#L131-L137
generic

jitsi-meet-electron-sdk/screensharing/main.js at 002dae740e63a225c0bc8ed7bd53ed7ce104ebc8 · jitsi/jitsi-meet-electron-sdk · GitHub

https://github.com/jitsi/jitsi-meet-electron-sdk/blob/002dae740e63a225c0bc8ed7bd53ed7ce104ebc8/screensharing/main.js#L93-L96
github_commit

commit 144080fdddad (jitsi/jitsi-meet-electron-sdk)

Fix landed in jitsi/jitsi-meet-electron-sdk commit 144080fdddad — awaiting tagged release

https://github.com/jitsi/jitsi-meet-electron-sdk/commit/144080fdddad2d11f7380475d4ac9bcf379cd035
github_pr

fix(screensharing): gate desktop source access on a user-initiated share

Fix merged in jitsi/jitsi-meet-electron-sdk PR #516 on 2026-09-07 — awaiting tagged release

https://github.com/jitsi/jitsi-meet-electron-sdk/pull/516

Vendor Advisories for CVE-2026-92299(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 28× in last 7d / 44× 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-09-25 10:24 UTCGHSA enrichment
  2. 2026-09-24 23:02 UTCEG score recompute
  3. 2026-09-24 23:02 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-24 11:06 UTCGHSA enrichment
  6. 2026-09-23 23:45 UTCEG score recompute
  7. 2026-09-23 23:45 UTCGHSA enrichment
  8. 2026-09-23 17:54 UTCEPSS rescore
  9. 2026-09-23 12:23 UTCGHSA enrichment
  10. 2026-09-23 01:01 UTCEG score recompute
  11. 2026-09-23 01:01 UTCGHSA enrichment
  12. 2026-09-22 16:01 UTCEPSS rescore
  13. 2026-09-22 13:39 UTCGHSA enrichment
  14. 2026-09-22 02:18 UTCEG score recompute
  15. 2026-09-22 02:17 UTCGHSA enrichment
  16. 2026-09-21 21:09 UTCEPSS rescore
  17. 2026-09-21 14:55 UTCGHSA enrichment
  18. 2026-09-21 03:25 UTCEG score recompute
  19. 2026-09-21 03:25 UTCGHSA enrichment
  20. 2026-09-20 20:16 UTCEPSS rescore
  21. 2026-09-20 16:03 UTCGHSA enrichment
  22. 2026-09-20 04:40 UTCGHSA enrichment
  23. 2026-09-19 17:18 UTCEG score recompute
  24. 2026-09-19 17:18 UTCGHSA enrichment
  25. 2026-09-19 05:56 UTCEG score recompute
Show 19 more
  1. 2026-09-19 05:56 UTCGHSA enrichment
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 18:35 UTCGHSA enrichment
  4. 2026-09-18 07:07 UTCGHSA enrichment
  5. 2026-09-17 19:46 UTCEG score recompute
  6. 2026-09-17 19:46 UTCGHSA enrichment
  7. 2026-09-17 19:32 UTCEPSS rescore
  8. 2026-09-17 08:24 UTCGHSA enrichment
  9. 2026-09-16 21:02 UTCGHSA enrichment
  10. 2026-09-16 19:24 UTCEG score recompute
  11. 2026-09-16 19:24 UTCGHSA enrichment
  12. 2026-09-16 18:52 UTCEG score recompute
  13. 2026-09-16 18:52 UTCGHSA enrichment
  14. 2026-09-16 14:09 UTCEPSS rescore
  15. 2026-09-16 13:48 UTCEG score recompute
  16. 2026-09-16 13:48 UTCGHSA enrichment
  17. 2026-09-16 02:25 UTCEG score recompute
  18. 2026-09-16 02:03 UTCEG score recompute
  19. 2026-09-16 02:02 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92299?
CVE-2026-92299 is a high vulnerability published on September 16, 2026. @jitsi/electron-sdk before 10.0.5 exposes getDesktopSources() via contextBridge without requiring an active getDisplayMedia() picker, allowing any script in the meeting page to enumerate screens and windows. Attackers can call the jitsi-screen-sharing-get-sources IPC route to retrieve desktop…
When was CVE-2026-92299 disclosed?
CVE-2026-92299 was first published in the National Vulnerability Database on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92299 actively exploited?
CVE-2026-92299 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 61.6% of all scored CVEs.
What is the CVSS score of CVE-2026-92299?
CVE-2026-92299 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-92299?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92299, 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

Explore the affected products and dependency analysis for CVE-2026-92299

Explore →

Is Your Infrastructure Affected by CVE-2026-92299?

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