CVE-2026-134316 is a vulnerability in better-auth/electron versions 1.5.0-beta.12 before 1.7.16 and 1.8.0-beta.0 before 1.8.0-beta.5. It allows authenticated users to obtain sensitive authentication secrets, including auth secrets and social provider client secrets, by accepting any validly signed transfer cookie and returning full endpoint context in sign-in responses. This enables session forgery as other users. Additionally, attackers who know a password can bypass two-factor authentication by exchanging desktop authorization codes issued before two-factor verification.
Electron versions prior to 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.5 have a vulnerability where HID and USB permission checks made from iframes can be attributed to the wrong origin. This occurs because the permission check handler receives the top-level frame's origin instead of the requesting iframe's origin, potentially allowing embedded frames to gain access intended only for the top-level page. The issue affects apps using origin-based logic in setPermissionCheckHandler for HID or USB permissions and embedding cross-origin iframes with these permissions allowed. The vulnerability has a medium severity with a CVSS score of 5.4 and has been fixed in the specified versions.
A local race condition vulnerability exists in the Squirrel.Mac auto-update framework bundled with Electron on macOS. The privileged ShipIt helper, which runs as root to complete updates, can be tricked by a local attacker to overwrite files of a different application instead of the intended one. This affects only Electron apps on macOS that use Squirrel.Mac-based auto-updates. No workarounds exist other than updating to a patched Electron version.
Electron versions prior to 41.10.4, between 42.0.0-alpha.1 and 42.5.2, and between 43.0.0-alpha.1 and 43.0.0 allowed popups opened from sandboxed iframes with 'allow-scripts allow-popups' to drop sandbox restrictions. This enabled sandboxed content to open popups with the embedding app's full origin, potentially accessing cookies, storage, and same-origin scripting. The issue affects apps embedding untrusted content in sandboxed iframes with these permissions. Fixed versions are 41.10.4, 42.5.2, and 43.0.0.
Electron versions prior to 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5 contain a vulnerability where windows opened from a sandboxed top-level document do not inherit the document's HTML sandbox restrictions. This allows sandboxed content to open new windows with the app's full origin, potentially escalating privileges. The issue affects apps rendering untrusted content in sandboxed top-level documents that allow popups. Apps that deny popups from untrusted content using setWindowOpenHandler are not affected. Fixes are available in the specified versions.
Electron versions prior to 41.10.6, between 42.0.0-alpha.1 and 42.9.2, between 43.0.0-alpha.1 and 43.4.1, and between 44.0.0-alpha.1 and 44.0.0-beta.5 have a vulnerability where file and HTTP protocol handlers allow cross-origin reads without the corsEnabled flag. This affects apps that register custom schemes with supportFetchAPI enabled but corsEnabled disabled and load untrusted content. The vulnerability allows cross-origin reading of responses, completing a previous fix (CVE-2026-70604). Fixed versions include 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5. Setting corsEnabled to true or avoiding loading untrusted content mitigates the issue.
A vulnerability in Electron's <webview> tag allows Node.js integration to be enabled in Web Workers even when the embedder disables it, potentially granting guest content elevated privileges. This affects applications that enable the <webview> tag and run without sandboxing. The issue is fixed in Electron versions 41.10.6, 42.9.2, 43.4.1, and 44.0.0-beta.5. Workarounds include removing nodeIntegrationInWorker from guest preferences or avoiding <webview> usage with untrusted content.
A vulnerability in Electron's sandboxed preload script caching allows a compromised renderer process to poison the cache and execute arbitrary code in the preload context on subsequent loads. This affects applications that load untrusted content. Fixed versions have been released, and updating is required as no application-side workarounds exist.
A vulnerability in Electron allows sandboxed iframes to launch external protocol handlers without respecting sandbox restrictions. This affects apps rendering untrusted content in sandboxed iframes that grant the openExternal permission by default. The issue is fixed in Electron versions 39.8.8, 40.9.0, 41.2.1, and 42.0.0-beta.3.
A vulnerability in Electron's DevTools allows the 'reveal in file manager' action to execute arbitrary files instead of just revealing them. This can be exploited if an attacker can run scripts inside the DevTools frontend, such as via a malicious DevTools extension. Only applications that open DevTools on windows displaying untrusted content or load untrusted DevTools extensions are affected. Fixed versions are 39.8.9 and later.
A vulnerability in Electron's contextBridge allows objects copied from untrusted content to carry attacker-influenced prototypes, enabling prototype-pollution-style attacks against preload code despite context isolation. This affects apps that accept object arguments from untrusted content and read their properties without own-property checks. The issue is fixed in Electron versions 39.8.9 and later.
A vulnerability in Electron allows JavaScript injection in the DevTools frontend via an unsanitized 'mode' parameter passed to webContents.openDevTools(). This can lead to script execution in the DevTools context, which may have Node.js access in unsandboxed configurations. The issue affects applications that allow untrusted input to influence the 'mode' argument or permit untrusted content to call openDevTools on embedded webviews. Fixed versions are 39.8.7 and later.
A vulnerability in Electron allows sandboxed iframes without the 'allow-popups' permission to open new windows or trigger setWindowOpenHandler without user interaction. This occurs because new-window navigations using the OpenURL path do not enforce the iframe sandbox popup restriction. Applications embedding untrusted content in sandboxed iframes and relying solely on the absence of 'allow-popups' to prevent window creation are affected. Versions prior to 39.8.10 are vulnerable. Fixed versions include 39.8.10, 41.10.3, and 42.0.1.
A vulnerability in Electron allows untrusted web content to control certain privileged window options via the window.open() features string. This can lead to the main process accessing attacker-chosen file or network paths if the app does not restrict or override these options. The issue affects Electron versions before 39.8.8 and is mitigated by denying window.open() calls from untrusted content or explicitly overriding window options. Fixed versions include 39.8.8 and later.
Electron versions prior to 40.10.6, 41.9.1, 42.5.1, and 43.0.0 contain a vulnerability where a custom protocol handler returning a ProtocolResponse with a url but without an explicit session causes the request to use the default session cache. This leads to potential cache reuse across isolated session partitions, undermining session isolation. Applications that explicitly set the session or do not isolate content across sessions are not affected. A fix is available in the specified versions.
Electron versions prior to 39.8.8 have a vulnerability where HTTP redirects followed by net.fetch() and net.request() are not restricted by scheme. This allows a remote server to redirect a request to a local resource, potentially disclosing local file contents if the app exposes the response body. Only apps making net requests to attacker-controlled URLs with redirects followed and response bodies exposed are affected. Fixed versions include 39.8.8 and later.
A vulnerability in Electron allows cross-origin reads from custom protocols that have supportFetchAPI enabled but lack CORS enforcement. This flaw permits remote-origin pages to fetch or XMLHttpRequest such schemes and read full response bodies without CORS restrictions. Applications serving sensitive data via such custom schemes and loading untrusted content are at risk. The issue is fixed in Electron versions 39.8.10, 40.9.3, 41.4.0, and 42.0.0.
A vulnerability in Electron's extension tab and scripting APIs allowed extensions loaded in one session to access and manipulate windows in other sessions. This affects apps that load Chrome extensions via session.loadExtension and rely on session separation for isolation. The issue is fixed in Electron versions 39.8.8 and later.
Electron's shell.openPath() function did not properly reject file paths containing embedded null bytes. This allowed attackers to bypass string-only validation checks on file paths, potentially causing the application to open a different file than intended. The issue affects apps that pass untrusted input to shell.openPath() without performing filesystem-level validation. Versions prior to 39.8.6 are vulnerable. The vulnerability has been fixed in versions 39.8.6, 40.9.0, 41.1.1, and 42.0.0-beta.1.
Electron versions prior to 39.8.9 are vulnerable to a context isolation bypass via hijacking Function.prototype.bind. This affects apps that expose Promise-returning functions to web content through contextBridge, potentially allowing untrusted web content to access the isolated preload environment and escalate privileges to Node.js access in certain configurations. The vulnerability is fixed in Electron versions 39.8.9 and later.