CVE-2026-113797

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

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 [email protected]

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.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-113797 has a CVSS score of 3.1 (Low). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (45.0.0-alpha.4, 44.1.1, 43.5.1, 42.11.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-113797? CVE-2026-113797 is a low-severity missing authorization vulnerability in electron (npm), affecting versions >= 45.0.0-alpha.1, < 45.0.0-alpha.4. It is fixed in 45.0.0-alpha.4, 44.1.1, 43.5.1, 42.11.1. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-113797? CVE-2026-113797 has a CVSS score of 3.1 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of electron are affected by CVE-2026-113797? electron (npm) versions >= 45.0.0-alpha.1, < 45.0.0-alpha.4 is affected.
4. Is there a fix for CVE-2026-113797? Yes. CVE-2026-113797 is fixed in 45.0.0-alpha.4, 44.1.1, 43.5.1, 42.11.1. Upgrade to this version or later.
5. Is CVE-2026-113797 exploitable, and should I be worried? Whether CVE-2026-113797 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-113797 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-113797?
   • Upgrade electron to 45.0.0-alpha.4 or later
   • Upgrade electron to 44.1.1 or later
   • Upgrade electron to 43.5.1 or later
   • Upgrade electron to 42.11.1 or later

Other vulnerabilities in electron