/

CVE-2026-92299

Severity:

HIGH RISK

(7.4)

Missing Authorization (CWE-862) in Jitsi Electron SDK

CVE-2026-92299

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Unauthorized Desktop and Window Information Disclosure

Severity:

HIGH RISK

(7.4)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A missing authorization check in the Jitsi Electron SDK exposes desktop-source enumeration to scripts running in a meeting page. A malicious or compromised script may retrieve thumbnails of screens and application windows without an active screen-sharing request, user consent, or an operating system permission prompt.

Affected context

The issue can occur in Electron-based Jitsi applications that expose the desktop-source retrieval function through the renderer context bridge. It becomes risky when page-controlled JavaScript can reach the associated IPC route without first passing through the normal getDisplayMedia() picker flow or an equivalent user-authorization decision.

Exploit preconditions

  • Attack surface: JavaScript running in a Jitsi meeting page and the Electron renderer-to-main-process bridge
  • Required access: Ability to execute script in the meeting page, such as through a compromised page, injected content, or another script-execution issue
  • Trigger point: Invocation of the exposed desktop-source enumeration interface and its associated IPC route
  • Why exploitation is possible: The bridge permits source retrieval without verifying an active media request, an approved selection, or an equivalent authorization state

Why this happens

The underlying flaw is an authorization decision missing from a privileged desktop-capture interface. The application exposes a capability that can enumerate screens and windows, but does not adequately bind that capability to a user-approved getDisplayMedia() request. This behavior maps to CWE-862: Missing Authorization, where access to a protected operation is not checked before the operation is performed.

Potential impact

  • An attacker may obtain thumbnails of available screens and application windows
  • Sensitive visual information may be disclosed without explicit user consent
  • The issue could reveal confidential documents, messages, credentials, or internal application data visible on a desktop
  • Repeated enumeration can increase surveillance and privacy risks during meetings

General mitigation guidance

Mitigation generally focuses on making desktop-source enumeration inaccessible by default and requiring an explicit, verifiable authorization context for every request.

Common defensive patterns include:

  • Exposing capture APIs only through a user-initiated and currently active media-selection flow
  • Enforcing authorization checks in the privileged process rather than relying solely on renderer-side controls
  • Avoiding unrestricted context-bridge exposure of desktop-source enumeration functions
  • Returning only the minimum source metadata required for an approved capture operation
  • Isolating meeting-page content from privileged Electron capabilities
  • Applying least privilege to IPC handlers and rejecting requests without a valid authorization token or state

How teams detect issues like this

Organizations can assess this class of issue through:

  • Static analysis for contextBridge APIs that expose privileged IPC or desktop-capture functions
  • Code review checks verifying authorization at the main-process IPC handler
  • Tests confirming that source enumeration fails without an active, user-approved media request
  • Policy enforcement requiring renderer-to-main interfaces to define explicit authorization and data-minimization behavior
  • Runtime telemetry for desktop-source enumeration that occurs outside approved capture workflows

Automated security review tools may help identify exposed bridge methods, missing authorization branches, and overly broad IPC handlers.

Sources

SourceLink
github.comgithub.com/jitsi/jitsi-meet-electron-sdk
github.comgithub.com/jitsi/jitsi-meet-electron-sdk/blob/002dae740e63a225c0bc8ed7bd53ed7ce104ebc8/screensharing/main.js#L93-L96
github.comgithub.com/jitsi/jitsi-meet-electron-sdk/blob/v10.0.5/screensharing/main.js#L131-L137
github.comgithub.com/jitsi/jitsi-meet-electron-sdk/commit/144080fdddad2d11f7380475d4ac9bcf379cd035
github.comgithub.com/jitsi/jitsi-meet-electron-sdk/pull/516
vulncheck.comvulncheck.com/advisories/jitsi-electron-sdk-before-10.0.5-unauthorized-screen-capture

Frequently asked

questions

It may be exploitable through content or scripts running in a meeting page, depending on the application's content-isolation and injection defenses. It does not require the attacker to directly access the user's operating system.

The attacker generally needs script execution within a page that can access the exposed context-bridge capability. The precise scope depends on renderer isolation, origin restrictions, and other application controls.

Require a verified user-approved capture flow before allowing desktop-source enumeration, and enforce that authorization in the privileged process handling the IPC request.

Minimize context-bridge APIs, apply least privilege to IPC routes, test denied requests by default, and ensure that sensitive desktop-capture operations are tied to explicit user intent and operating system controls.

Find out what's already
exploitable in your codebase.