How severe is GHSA-98mx-cjp9-gchm?

GHSA-98mx-cjp9-gchm has a CVSS score of 3.1/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-98mx-cjp9-gchm?

GHSA-98mx-cjp9-gchm affects the following packages: electron (npm), electron (npm), electron (npm), electron (npm). Ecosystems affected: npm.

How do I fix GHSA-98mx-cjp9-gchm?

Update electron to 45.0.0-alpha.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-98mx-cjp9-gchm is resolved across your whole dependency graph.

How do I detect GHSA-98mx-cjp9-gchm in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-98mx-cjp9-gchm if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-98mx-cjp9-gchm actively exploited in the wild?

No public exploit code has been indexed for GHSA-98mx-cjp9-gchm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-98mx-cjp9-gchm?

GHSA-98mx-cjp9-gchm has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 41th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-98mx-cjp9-gchm?

GHSA-98mx-cjp9-gchm is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-98mx-cjp9-gchm published, and has it been updated?

GHSA-98mx-cjp9-gchm was published on October 22, 2026 and was last updated on October 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

LOW severity

Electron: Extension tabs.query returns tab URLs and titles without the tabs permissionGHSA-98mx-cjp9-gchm

LOWFix: electron/electron#53356

GHSA-98mx-cjp9-gchm is a low-severity (CVSS 3.1) CWE-862 vulnerability in electron. A fix is available for electron — see the affected versions and patch details below.

Also known asCVE-2026-113797

Published

Oct 22, 2026

Updated

Oct 22, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-98mx-cjp9-gchm by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

4 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

2Kother npm packages depend on this — each one inherits the vulnerability until it's patched upstream

electronnpm

5.3Mdownloads / week

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

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`electron`	≥ 45.0.0-alpha.1&&< 45.0.0-alpha.4	45.0.0-alpha.4`npm install electron@45.0.0-alpha.4`
📦npm	`electron`	≥ 44.0.0-alpha.1&&< 44.1.1	44.1.1`npm install electron@44.1.1`
📦npm	`electron`	≥ 43.0.0-alpha.1&&< 43.5.1	43.5.1`npm install electron@43.5.1`
📦npm	`electron`	all versions	42.11.1`npm install electron@42.11.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for electron, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update electron to 45.0.0-alpha.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-98mx-cjp9-gchm is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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` *