GHSA-98mx-cjp9-gchm CVE-2026-113797

Electron: Extension tabs.query returns tab URLs and titles without the tabs permission

Low npm

Severity: 3.1 / 10; Low · CVSS 3.1
Exploit chance (EPSS): 0.59%; Chance of exploitation in the next 30 days. Higher than 48.00% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-862 Missing Authorization
Fix: 45.0.0-alpha.4; Upgrade electron to this version or later

Description

Impact

chrome.tabs.query() returned each tab's url and title to extensions that held neither the tabs permission nor matching host permissions, so any loaded extension could read the URL and title of every webContents in its session.

Apps are only affected if they load extensions (session.extensions.loadExtension) that they do not fully trust. Apps that load no extensions, or only trusted ones, are not affected.

Workarounds

Do not load untrusted or unvalidated extensions. In general you should only load trusted extensions.

Fixed Versions

45.0.0-alpha.4
44.1.1
43.5.1
42.11.1

For more information

If you have any questions or comments about this advisory, email us at security@electronjs.org

Affected versions

npm

Package	Vulnerable	Fixed in
electron	`>= 45.0.0-alpha.1, < 45.0.0-alpha.4`	`45.0.0-alpha.4`
electron	`>= 44.0.0-alpha.1, < 44.1.1`	`44.1.1`
electron	`>= 43.0.0-alpha.1, < 43.5.1`	`43.5.1`
electron	`< 42.11.1`	`42.11.1`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

electron npm → `45.0.0-alpha.4`

npm

npm install electron@45.0.0-alpha.4

yarn

yarn add electron@45.0.0-alpha.4

pnpm

pnpm add electron@45.0.0-alpha.4

Severity breakdown

CVSS 3.1 3.1

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

Attack vector: Network
Attack complexity: High
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Weakness

CWE-862: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

How to prevent it

Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2026-113797

Packages

github.com/electron/electron

Timeline

Oct 21, 2026 Published
Oct 28, 2026 Last updated by the source
Nov 1, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-qqvq-6xgj-jw8g Electron affected by libvpx's heap buffer overflow in vp8 encoding	High Known exploited	Also affects electron
GHSA-j7hp-h8jx-5ppr libwebp: OOB write in BuildHuffmanTable	High Known exploited	Also affects electron
GHSA-995f-9x5r-2rcj Heap buffer overflow in GPU	Critical Known exploited	Also affects electron
GHSA-jr5w-w6x2-84p9 Electron: Mitigation for compromised eMudhra intermediate certificates	High	Also affects electron
GHSA-h3v5-h239-pg29 Electron: Off-screen rendering on macOS trusts GPU-supplied frame geometry	Low	Also affects electron
GHSA-3qxv-5xgr-q7w9 Electron: Frame subscription trusts GPU-supplied frame geometry	Low	Also affects electron
GHSA-997q-gvvc-jwmx Electron: openExternal permission requests can be attributed to the wrong origin	Medium	Also affects electron
GHSA-fw47-9c62-h3vw Electron: HID and USB permission checks can be attributed to the wrong origin	Medium	Also affects electron

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor