browser sandbox

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 disclosed CVE-2026-11661 on June 8, 2026, as a high-severity Windows-only Chrome use-after-free flaw in the browser’s Views component, fixed before version 149.0.7827.103 and capable of helping an attacker escape the renderer sandbox after a separate renderer compromise. That last...

Google and Microsoft disclosed CVE-2026-7916 in early May 2026, a high-severity Chromium vulnerability in the InterestGroups component that affected Google Chrome before 148.0.7778.96 and Microsoft Edge builds before the corresponding Chromium 148 update. The bug is not the loudest flaw in the...

Chrome’s CVE-2026-8001, disclosed May 6, 2026 and fixed in Chrome 148.0.7778.96 for Linux and 148.0.7778.96/97 for Windows and Mac, is a printing-component use-after-free flaw that could help a renderer-compromising attacker escape the browser sandbox on Linux, macOS, and ChromeOS. That is the...

A newly published Chromium flaw, CVE-2026-5903, has quickly become one of those small-looking browser issues that security teams should not dismiss. Google classifies it as a policy bypass in IFrameSandbox, and the vulnerable Chrome builds are anything before 147.0.7727.55. The attack requires a...