What is CVE-2026-113798?

CVE-2026-113798 is a medium-severity security vulnerability in electron (npm), affecting versions >= 45.0.0-alpha.1, < 45.0.0-alpha.13. It is fixed in 45.0.0-alpha.13, 44.5.0, 43.7.6, 42.11.9.

How severe is CVE-2026-113798?

CVE-2026-113798 has a CVSS score of 5.4 (Medium). 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.

Which versions of electron are affected by CVE-2026-113798?

electron (npm) versions >= 45.0.0-alpha.1, < 45.0.0-alpha.13 is affected.

Is there a fix for CVE-2026-113798?

Yes. CVE-2026-113798 is fixed in 45.0.0-alpha.13, 44.5.0, 43.7.6, 42.11.9. Upgrade to this version or later.

Is CVE-2026-113798 exploitable, and should I be worried?

Whether CVE-2026-113798 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.

What actually determines whether CVE-2026-113798 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.

CVE-2026-113798 in electron

Q: How severe is CVE-2026-113798?

CVE-2026-113798 has a CVSS score of 5.4 (Medium). 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.

Q: Which versions of electron are affected by CVE-2026-113798?

electron (npm) versions >= 45.0.0-alpha.1, < 45.0.0-alpha.13 is affected.

Q: Is there a fix for CVE-2026-113798?

Yes. CVE-2026-113798 is fixed in 45.0.0-alpha.13, 44.5.0, 43.7.6, 42.11.9. Upgrade to this version or later.

Q: Is CVE-2026-113798 exploitable, and should I be worried?

Whether CVE-2026-113798 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.

Q: What actually determines whether CVE-2026-113798 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.

Q: How do I fix CVE-2026-113798?

Upgrade: electron to 45.0.0-alpha.13 or later, electron to 44.5.0 or later, electron to 43.7.6 or later, electron to 42.11.9 or later.

Summary

Electron: Pointer lock permission requests can be attributed to the wrong frame

Workarounds

Deny the pointerLock permission for web contents that embed untrusted frames.

Fixed Versions

45.0.0-alpha.13
44.5.0
43.7.6
42.11.9

For more information

If you have any questions or comments about this advisory, email us at [email protected]

Impact

For pointerLock permission requests made from some cross-origin iframes, session.setPermissionRequestHandler() was given the top-level frame's requestingUrl and isMainFrame instead of the requesting frame's. Apps that grant pointer lock based on the requesting origin could grant it to embedded content under the top-level page's identity.

Apps are only affected if they embed untrusted content in iframes and decide pointerLock requests by origin in setPermissionRequestHandler. Apps that do not embed untrusted content, or that deny pointerLock for it, are not affected.

CVE-2026-113798 has a CVSS score of 5.4 (Medium). 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.13, 44.5.0, 43.7.6, 42.11.9); upgrading removes the vulnerable code path.

Affected versions

electron (>= 45.0.0-alpha.1, < 45.0.0-alpha.13) electron (>= 44.0.0-alpha.1, < 44.5.0) electron (>= 43.0.0-alpha.1, < 43.7.6) electron (< 42.11.9)

Security releases

electron → 45.0.0-alpha.13 (npm) electron → 44.5.0 (npm) electron → 43.7.6 (npm) electron → 42.11.9 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

electron to 45.0.0-alpha.13 or later; electron to 44.5.0 or later; electron to 43.7.6 or later; electron to 42.11.9 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-113798? CVE-2026-113798 is a medium-severity security vulnerability in electron (npm), affecting versions >= 45.0.0-alpha.1, < 45.0.0-alpha.13. It is fixed in 45.0.0-alpha.13, 44.5.0, 43.7.6, 42.11.9.
How severe is CVE-2026-113798? CVE-2026-113798 has a CVSS score of 5.4 (Medium). 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.
Which versions of electron are affected by CVE-2026-113798? electron (npm) versions >= 45.0.0-alpha.1, < 45.0.0-alpha.13 is affected.
Is there a fix for CVE-2026-113798? Yes. CVE-2026-113798 is fixed in 45.0.0-alpha.13, 44.5.0, 43.7.6, 42.11.9. Upgrade to this version or later.
Is CVE-2026-113798 exploitable, and should I be worried? Whether CVE-2026-113798 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
What actually determines whether CVE-2026-113798 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.
How do I fix CVE-2026-113798?
- Upgrade electron to 45.0.0-alpha.13 or later
- Upgrade electron to 44.5.0 or later
- Upgrade electron to 43.7.6 or later
- Upgrade electron to 42.11.9 or later

Other vulnerabilities in electron

CVE-IDSeverityPackage summary

CVE-2026-113796Mediumelectron: Electron: SameSite cookie restrictions are not applied to windows opened from links CVE-2026-113797Lowelectron: Electron: Extension tabs.query returns tab URLs and titles without the tabs permission CVE-2026-114122Lowelectron: Electron: Frame subscription trusts GPU-supplied frame geometry CVE-2026-114124Lowelectron: Electron: Off-screen rendering on macOS trusts GPU-supplied frame geometry CVE-2026-114121Mediumelectron: Electron: openExternal permission requests can be attributed to the wrong origin