Loading story…
Electron disclosed two high-severity vulnerabilities affecting desktop applications built on the framework, including a context isolation bypass tracked as CVE-2026-34780 and a use-after-free bug tracked as CVE-2026-34774. The first flaw lets an attacker who can run JavaScript in the main world—such as through XSS—abuse WebCodecs VideoFrame objects passed across contextBridge to reach the isolated world and potentially access Node.js APIs exposed by preload scripts. It affects Electron 39.0.0-alpha.1 through before 39.8.0, 40.0.0-alpha.1 through before 40.7.0, and 41.0.0-alpha.1 through before 41.0.0-beta.8.
The second issue affects applications that use offscreen rendering and allow child windows via window.open(). If a parent offscreen WebContents is destroyed while a child window remains open, later paint callbacks in the child can dereference freed memory, leading to crashes or memory corruption. Electron patched the flaws in versions 39.8.0, 40.7.0, and 41.0.0-beta.8 for CVE-2026-34780, and in 39.8.1, 40.7.0, and 41.0.0 for CVE-2026-34774; apps that do not pass VideoFrame objects through contextBridge, do not enable offscreen rendering, or block child windows are not exposed to the respective bugs.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
Electron disclosed CVE-2026-34774, a use-after-free vulnerability in offscreen child window paint handling when a parent offscreen WebContents is destroyed while a child window remains open. The flaw affects versions prior to 39.8.1, 40.7.0, and 41.0.0, and Electron patched it in those releases.
Electron disclosed CVE-2026-34780, a context isolation bypass involving WebCodecs VideoFrame objects passed across contextBridge. The issue affects Electron 39.0.0-alpha.1 through before 39.8.0, 40.0.0-alpha.1 through before 40.7.0, and 41.0.0-alpha.1 through before 41.0.0-beta.8, and was patched in versions 39.8.0, 40.7.0, and 41.0.0-beta.8.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A vulnerability tracked as **CVE-2026-70609** was disclosed in **Electron**, where an unsanitized `dock-state` parameter could allow **JavaScript injection into Electron DevTools** under the conditions described in the advisory. Public reporting said the issue was fixed by Electron, and the CVE record and upstream advisory were cited as corroborating both the flaw and its remediation. The issue appeared alongside broader vulnerability tracking in Striga’s CVE roundup, which listed multiple high- and critical-severity flaws across products including **n8n**, **FreshRSS**, **Apache httpd**, **Apache Shiro**, **Apache Tomcat**, **axios**, and **Mattermost Desktop**. Separate reporting noted that while Striga attributed discovery of the Electron flaw to an AI system, upstream records credited a human reporter and did not independently confirm the AI attribution.
Aug 19, 2026
Google Chrome patched two high-severity vulnerabilities affecting desktop builds on **Windows, Linux, and macOS** before version `146.0.7680.178`. The first, `CVE-2026-5282`, is an out-of-bounds read in **WebCodecs** that could be triggered if a user opens a crafted HTML page, potentially exposing sensitive memory and causing a crash. NVD classified the flaw as `CWE-125` and scored it with the vector `AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H`, indicating remote exploitation with low complexity but requiring user interaction. The second flaw, `CVE-2026-5289`, is a **use-after-free** in Chrome's **Navigation** component that could allow an attacker who has already compromised the renderer process to potentially escape the browser sandbox through a crafted HTML page. NVD mapped the issue to `CWE-416` and assigned the vector `AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`, reflecting the risk of broader compromise across confidentiality, integrity, and availability. Google referenced both issues in its Chrome stable channel advisory and linked them to Chromium issue tracker entries, making version `146.0.7680.178` the key remediation point for affected users and enterprises.
Jun 29, 2026
Google disclosed two high-severity use-after-free vulnerabilities in Chrome, **CVE-2026-6302** and **CVE-2026-6304**, affecting versions prior to **`147.0.7727.101`**. The flaws reside in the browser's **Video** and **Graphite** components and can be triggered with a crafted HTML page. **CVE-2026-6302** could allow a remote attacker to execute arbitrary code inside the sandbox, while **CVE-2026-6304** could let an attacker who has already compromised the renderer process potentially escape Chrome's sandbox. Both issues are classified as **`CWE-416`** use-after-free bugs and were rated **High** severity by Chromium. The published CVSS v3.1 vectors indicate significant potential impact to confidentiality, integrity, and availability, with **CVE-2026-6302** scored as **`AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`** and **CVE-2026-6304** as **`AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H`**. Organizations running Chrome should prioritize upgrading to **`147.0.7727.101`** or later to mitigate the risk from malicious web content targeting these memory-safety flaws.
Jun 29, 2026