chrome security

  1. Chrome CVE-2026-6302 Patched: Use-After-Free Video Bug Enables Sandbox RCE

    Google has patched CVE-2026-6302, a high-severity use-after-free flaw in Chrome’s Video component, in Chrome version 147.0.7727.101 for Linux and 147.0.7727.101/102 for Windows and Mac. The issue could let a remote attacker achieve arbitrary code execution inside the browser sandbox by luring a...
  2. CVE-2026-6299: Critical Chrome Prerender Use-After-Free Patch (Apr 15, 2026)

    The latest Chromium security cycle has put CVE-2026-6299 under a harsh spotlight because it combines three things defenders hate to see together: a use-after-free bug, a critical Chromium severity rating, and a fix that lands in a browser engine used by far more than just Google Chrome...
  3. CVE-2026-6297 Critical Chrome Proxy Use-After-Free: Patch to 147.0.7727.101

    Google has patched CVE-2026-6297, a use-after-free in Proxy that affects Chrome versions before 147.0.7727.101 and carries a Critical Chromium severity rating. The public description says a crafted HTML page could allow an attacker in a privileged network position to potentially achieve a...
  4. CVE-2026-6312 Chrome Passwords Flaw: Cross-Origin Data Leak Fixed in 147.0.7727.101

    Insufficient policy enforcement bugs in Chromium continue to be a reminder that browser security is often won or lost at the seams between isolation boundaries, not just in the core rendering engine. CVE-2026-6312 fits that pattern: Google says a remote attacker who had already compromised the...
  5. CVE-2026-6301: High Turbofan Type Confusion Lets Attacker Execute Code in Chrome

    By all appearances, CVE-2026-6301 is exactly the kind of Chromium flaw that can turn a routine browser session into a serious enterprise security event. Google describes it as a type confusion in Turbofan, affecting Chrome versions prior to 147.0.7727.101, and says a crafted HTML page could let...
  6. CVE-2026-6300: Chrome CSS Use-After-Free—Update Now for Edge and Windows

    Google’s latest Chrome security cycle has landed with another high-severity memory-safety bug, and this one is especially important because it sits in CSS, one of the browser’s core layout engines. CVE-2026-6300 affects Google Chrome versions prior to 147.0.7727.101, and Google says a crafted...
  7. CVE-2026-6303 Chrome Codec Use-After-Free: Patch 147.0.7727.101/102 Now

    The latest Chromium security advisory for CVE-2026-6303 is a reminder that browser patching is still a race against exploitation. Google says the flaw is a use-after-free in Codecs affecting Chrome versions before 147.0.7727.101, and that a crafted HTML page could let a remote attacker execute...
  8. CVE-2026-6316 Chrome Forms Use-After-Free: Update to 147.0.7727.101

    Microsoft’s CVE-2026-6316 is a reminder that the most dangerous browser flaws are often the ones that sound almost mundane: a use-after-free in Forms. Google says the issue affects Chrome versions prior to 147.0.7727.101, can be triggered through a crafted HTML page, and may let a remote...
  9. Chrome CVE-2026-6360 Patched: High-Severity FileSystem Use-After-Free Fix

    Overview Google has patched a high-severity use-after-free vulnerability in Chrome’s FileSystem component, tracked as CVE-2026-6360, and the fix is now part of the Stable channel build 147.0.7727.101/102 for Windows and Mac and 147.0.7727.101 for Linux. The issue was disclosed in Google’s April...
  10. CVE-2026-6318 Chrome Codecs Use-After-Free: Update to 147.0.7727.101

    Google’s disclosure of CVE-2026-6318 is another reminder that the browser security story is still dominated by memory safety bugs, not just policy bypasses and UI tricks. The flaw is a use-after-free in Codecs affecting Google Chrome prior to 147.0.7727.101, and Google says a crafted HTML page...
  11. CVE-2026-6314 Chrome GPU Bug: Patch 147.0.7727.101/102 and Secure Edge

    The latest Chrome security cycle has landed with a high-severity GPU memory corruption bug that matters well beyond the browser tab where it originated. Google’s April 15, 2026 Stable Channel update for desktop includes CVE-2026-6314, described as an out-of-bounds write in GPU, and the fixed...
  12. CVE-2026-6362: Chrome Codecs Use-After-Free Fix for 147.0.7727.101/102

    Chromium’s latest security disclosure is a sharp reminder that browser code paths still sit at the center of modern attack surface. CVE-2026-6362 is a use-after-free in Codecs that affects Google Chrome versions prior to 147.0.7727.101, and Google says a remote attacker could potentially trigger...
  13. CVE-2026-6359: Chrome Use-After-Free in Video—Windows Edge Update Urgent

    The discovery of CVE-2026-6359 is a reminder that browser security issues rarely stop at the label attached to the bug. Google’s April 15, 2026 Chrome release shows the flaw is a use-after-free in Video, fixed in Chrome 147.0.7727.101/102 for Windows and Mac and 147.0.7727.101 for Linux, while...
  14. CVE-2026-6296 Critical ANGLE Heap Overflow: Patch Chrome 147 ASAP

    Chromium’s **CVE-2026-6296** is one of those browser bugs that looks routine on paper and alarming in practice: a **heap buffer overflow in ANGLE** that Google rated **Critical** and fixed in Chrome **147.0.7727.101** on April 15, 2026. The public description says a crafted HTML page could let a...
  15. CVE-2026-5866 Chrome Media Use-After-Free: Patch to 147.0.7727.55

    Google has published CVE-2026-5866, a use-after-free in Chrome’s Media component that can let a remote attacker execute code inside the browser sandbox through a crafted HTML page. The issue affects Google Chrome versions prior to 147.0.7727.55, and it has been assigned Chromium security...
  16. CVE-2026-5900: Chrome Download Policy Bypass and the 147.0.7727.55 Fix

    Chromium’s CVE-2026-5900 is a reminder that browser security issues do not need to be dramatic to matter operationally. Google says the flaw is a policy bypass in Downloads that affected Chrome versions prior to 147.0.7727.55, where a remote attacker could use a crafted HTML page to bypass...
  17. CVE-2026-5904 Chrome V8 Use-After-Free: Patch 147.0.7727.55 and Lock Extensions

    Chromium’s CVE-2026-5904 is a reminder that even “low-severity” browser bugs can become meaningful security issues when they sit inside a component as central as V8 and are reachable through a malicious extension. Google says the flaw is a use-after-free in Chrome versions prior to...
  18. CVE-2026-5907 Chrome Media Bug: OOB Read Risk and Patch Guidance

    Chromium’s CVE-2026-5907 is another reminder that browser security problems do not need to be flashy to matter. Google says the flaw is an insufficient data validation bug in Media that affects Chrome versions prior to 147.0.7727.55, and the practical result is a remote attacker being able to...
  19. CVE-2026-5908: Chrome 147.0.7727.55 Media Integer Overflow and Heap Corruption

    A newly published Chromium vulnerability, tracked as CVE-2026-5908, has put browser security teams back on alert just as Google pushed Chrome to version 147.0.7727.55. The flaw is an integer overflow in Media that can be triggered by a crafted video file, potentially leading to heap corruption...
  20. CVE-2026-5912: Chrome WebRTC Integer Overflow—Update to 147.0.7727.55 Now

    Overview Google’s newly published CVE-2026-5912 is a reminder that browser security remains a moving target, even in a product as mature and heavily instrumented as Chrome. The flaw is described as an integer overflow in WebRTC that could let a remote attacker trigger an out-of-bounds memory...