Loading story…
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.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
On April 1, 2026, CVE-2026-5289 was recorded as a high-severity use-after-free flaw in Chrome's Navigation component. The vulnerability could potentially allow a remote attacker, after compromising the renderer process, to escape the sandbox via a crafted HTML page.
On April 1, 2026, CVE-2026-5282 was recorded as a high-severity out-of-bounds read vulnerability in Chrome's WebCodecs component. Google and NVD described it as exploitable via a crafted HTML page that could trigger an out-of-bounds memory read when opened by a user.
On April 1, 2026, Google published a Chrome stable channel advisory indicating that versions prior to 146.0.7680.178 were affected by two high-severity vulnerabilities: CVE-2026-5282 in WebCodecs and CVE-2026-5289 in Navigation. The issues affected Chrome on Windows, Linux, and macOS.
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.
Google disclosed two high-severity Chrome vulnerabilities that could be triggered when a user visits a crafted HTML page, affecting the browser's **WebCodecs** and **V8** components. **`CVE-2026-5292`** is an out-of-bounds read in WebCodecs, tracked as **`CWE-125`**, and impacts Chrome versions prior to **`146.0.7680.178`**. The flaw carries a **CVSS v3.1** vector of **`AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`**, indicating remote exploitation with user interaction and potentially high impact to confidentiality, integrity, and availability. Google also recorded **`CVE-2026-6363`**, a **type confusion** issue in **V8** tracked as **`CWE-843`**, affecting Chrome versions prior to **`147.0.7727.101`**. Chrome rated the V8 bug with Medium Chromium security severity, but the published **CVSS v3.1** vector likewise reflects potentially high impact if exploited through malicious web content. Both vulnerabilities were documented in Chrome release materials and Chromium issue tracker entries, underscoring the need for organizations to update Chrome promptly to the patched versions.
Jun 29, 2026
Google Chrome addressed three **use-after-free** vulnerabilities tracked as `CVE-2026-7347`, `CVE-2026-7363`, and `CVE-2026-7344` in versions prior to `147.0.7727.138`. The bugs affect the **Chromoting**, **Canvas**, and **Accessibility** components, respectively, and all were classified under `CWE-416`. Two of the flaws were rated **critical**: `CVE-2026-7363` allows a remote attacker to execute arbitrary code inside the browser sandbox on Linux and ChromeOS by luring a user to a crafted HTML page, while `CVE-2026-7344` could let an attacker escape Chrome's sandbox on Windows after compromising the renderer process via crafted web content. The third issue, `CVE-2026-7347`, was rated **high severity** and affects Chromoting, where malicious network traffic could enable arbitrary code execution without privileges or user interaction. CVSS data added to the records shows network-based exploitation with high impact to confidentiality, integrity, and availability, with `CVE-2026-7363` and `CVE-2026-7344` carrying the vector `AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`. The vulnerabilities were documented in Chrome and Chromium tracking references, underscoring the need for organizations to move affected browsers to `147.0.7727.138` or later.
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