You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
chrome update
About this tag
The chrome update tag covers recent security patches for Google Chrome and Chromium-based browsers, focusing on high-severity vulnerabilities disclosed in 2026. Recurring themes include use-after-free and memory corruption flaws in components like WebCodecs, V8, PDFium, WebRTC, and MediaRecording, many of which allow remote code execution inside Chrome's sandbox. Several CVEs, such as CVE-2026-11645, were confirmed as actively exploited, emphasizing the urgency of applying updates. The content also discusses the broader implications for Windows users and enterprise administrators, including the need to verify version numbers and treat Chromium as a critical part of workstation attack surface. Practical advice centers on updating Chrome and Chromium-derived browsers promptly.
Google Chrome before 149.0.7827.103 contains CVE-2026-11683, a high-severity use-after-free flaw in WebCodecs disclosed on June 8, 2026, that can let a remote attacker run arbitrary code inside Chrome’s sandbox when a user opens a crafted HTML page. The practical instruction is simple: update...
Google Chrome before version 149.0.7827.103 contains CVE-2026-11678, a high-severity integer overflow in the libyuv image-processing library disclosed on June 8, 2026, that can let an attacker who already compromised Chrome’s renderer read potentially sensitive process memory through a crafted...
Google fixed CVE-2026-11670 on June 8, 2026, in Chrome’s desktop Stable channel update to version 149.0.7827.102/.103 for Windows and Mac and 149.0.7827.102 for Linux, closing a high-severity use-after-free flaw in Chrome’s built-in PDF handling. The vulnerability allowed remote code execution...
Google fixed CVE-2026-11645 on June 8, 2026, in Chrome 149.0.7827.102/.103 for desktop platforms after confirming active exploitation of a high-severity V8 out-of-bounds read/write flaw reachable through a crafted HTML page. The important phrase is not “high severity,” because browser teams ship...
Google and Microsoft disclosed CVE-2026-7929 on May 6, 2026, a high-severity use-after-free flaw in Chromium’s MediaRecording component fixed in Google Chrome 148.0.7778.96 for Linux and 148.0.7778.96/97 for Windows and macOS. The vulnerability matters because it sits in the browser’s media...
CVE-2026-7338 is a high-severity use-after-free flaw in Chromium’s Cast component, disclosed on April 28, 2026, and fixed in Google Chrome 147.0.7727.138 after researchers found local-network malicious traffic could potentially trigger heap corruption before the update. The vulnerability is not...
On April 28, 2026, Google shipped Chrome 147.0.7727.137/138 for Windows and macOS and 147.0.7727.137 for Linux, fixing CVE-2026-7336, a high-severity use-after-free flaw in WebRTC that could let a remote attacker run code inside Chrome’s sandbox through a crafted HTML page. The uncomfortable...
Google has patched a high-severity heap buffer overflow in PDFium that affects Chrome on Windows versions before 147.0.7727.101, closing off a path that could let an attacker execute code inside the browser sandbox through a crafted PDF. The fix landed in the April 15, 2026 Stable Channel...
Insufficient policy enforcement in CORS is exactly the kind of Chromium bug that looks narrow on paper and broad in practice, because it sits at the intersection of renderer compromise, cross-origin data boundaries, and the browser’s trust model. Google has assigned CVE-2026-6313 to that issue...
Google’s latest Chromium security disclosure, CVE-2026-5880, is a reminder that browser hardening is never just about fixing memory corruption. This flaw, assigned Chromium security severity: Medium, lets an attacker who has already compromised the renderer process spoof the contents of Chrome’s...
Chromium’s newly disclosed CVE-2026-5886 is a reminder that even a browser component as familiar as WebAudio can become a memory-safety risk with real-world impact. According to the record you provided, the flaw is an out-of-bounds read in Google Chrome on Mac prior to 147.0.7727.55, and a...
Google’s CVE-2026-5291 is another reminder that browser graphics code remains a high-value target, even when the issue is “only” classified as medium severity. Microsoft’s Security Update Guide mirrors the Chrome advisory and confirms the flaw affects Google Chrome prior to 146.0.7680.178, with...
CVE-2026-5284 is another reminder that modern browser security is rarely about a single flaw in isolation. The issue is a use-after-free in Dawn, Chrome’s WebGPU-related graphics stack, and Google says it could let a remote attacker who had already compromised the renderer process execute...
Google Chrome’s March 23, 2026 stable-channel security update closed a high-severity use-after-free in FedCM, tracked as CVE-2026-4680, and the affected builds were Chrome versions prior to 146.0.7680.165 on desktop. Google’s own release notes say the flaw could be reached through a crafted HTML...
Google’s decision to shift Chrome’s milestone releases to a two‑week cadence — beginning with Chrome 153, slated for a stable release on September 8, 2026 — marks the most aggressive update tempo the browser has used and will reshape how users, developers, and IT teams plan for browser change...
Google’s December stable update corrected two high‑severity Chromium issues — a use‑after‑free in WebGPU (CVE‑2025‑14765) and an out‑of‑bounds read/write in V8 (CVE‑2025‑14766) — and the fixes were rolled into Chrome stable (143.0.7499.146/.147), with downstream consumers such as Microsoft Edge...
Google released an emergency Chrome stable update that fixes a use‑after‑free (UAF) vulnerability in the WebRTC component tracked as CVE‑2025‑10501, and Microsoft Edge (Chromium‑based) customers should treat the issue as relevant until Microsoft ships the Chromium ingestion for Edge. Background...
Chromium developers have closed a high‑severity upstream bug — tracked as CVE‑2025‑10201 — that the Chromium project describes as an “inappropriate implementation in Mojo” which could be abused, via a crafted HTML page, to bypass Chrome’s site‑isolation protections on Android, Linux and...
Updating Chrome from the command line with Winget on Windows 11 turns a repetitive, GUI-driven maintenance task into a single, scriptable operation—saving time for power users and administrators while giving clear, auditable control over browser updates. The how-to that follows summarizes the...
A recently disclosed memory-safety flaw in Chromium’s Aura windowing component — tracked as CVE-2025-8882 — allows a remote attacker who can trick a user into specific UI gestures to trigger a use‑after‑free that may lead to heap corruption; the bug was patched upstream in Google Chrome...