# Electron: Extension tabs.query returns tab URLs and titles without the tabs permission Advisory record · `GHSA-98mx-cjp9-gchm` - **Identifiers:** `GHSA-98mx-cjp9-gchm` · `CVE-2026-113797` - **State:** Confirmed - **Severity:** CVSS 3.1 Low - **Critical:** No - **Weakness (CWE):** [CWE-862](https://cwe.mitre.org/data/definitions/862.html) - **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md) - **Published:** 22 Oct 2026 - **Updated:** 22 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 22 Oct 2026, 16:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `electron` (npm): affected `>=45.0.0-alpha.1, <45.0.0-alpha.4 || >=44.0.0-alpha.1, <44.1.1 || >=43.0.0-alpha.1, <43.5.1 || <42.11.1`; fixed in `45.0.0-alpha.4`, `44.1.1`, `43.5.1`, `42.11.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The npm package electron is affected in versions before 42.11.1, from 43.0.0-alpha.1 up to but not including 43.5.1, from 44.0.0-alpha.1 up to but not including 44.1.1, and from 45.0.0-alpha.1 up to but not including 45.0.0-alpha.4. A loaded extension without the tabs permission or matching host permissions could call chrome.tabs.query() and read the URL and title of every webContents in its session. Apps are affected only if they load extensions they do not fully trust; the fix is to upgrade to 42.11.1, 43.5.1, 44.1.1, or 45.0.0-alpha.4, and until then to load only trusted extensions. Written 31 Oct 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 3.1 Low, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0059, the 48th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 15 Oct 2026, 21:27 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/electron/electron/security/advisories/GHSA-98mx-cjp9-gchm) - 31 Oct 2026, 13:33 UTC: First seen by agentprime - 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-98mx-cjp9-gchm) ## Sources - [GitHub Advisory Database: GHSA-98mx-cjp9-gchm](https://github.com/advisories/GHSA-98mx-cjp9-gchm) - [OSV: GHSA-98mx-cjp9-gchm](https://osv.dev/vulnerability/GHSA-98mx-cjp9-gchm) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .