Chrome patches six Critical flaws, two found with AI’s help
What happened?
.kadence-column491003_6bab7a-f6 >.kt-inside-inner-col{padding-top:20px;padding-right:20px;padding-bottom:10px;padding-left:20px;}.kadence-column491003_6bab7a-f6 >.kt-inside-inner-col{column-gap:var(--global-kb-gap-sm, 1rem);}.kadence-column491003_6bab7a-f6 >.kt-inside-inner-col{flex-direction:column;}.kadence-column491003_6bab7a-f6 >.kt-inside-inner-col >.aligncenter{width:100%;}.kadence-column491003_6bab7a-f6 >.kt-inside-inner-col{background-color:rgba(255, 229, 229, 0.83);}.kadence-column491003_6bab7a-f6 >.kt-inside-inner-col:before{opacity:0.3;}.kadence-column491003_6bab7a-f6{position:relat…
Key details
- Anthropic researcher Xinyang Ge discovered two Critical flaws with assistance from the Claude AI system.
- Critical vulnerabilities involve memory-safety errors including out-of-bounds writes, buffer overflow, and use-after-free issues.
- Chrome 158.0.8127.42 for Android released with same security fixes, rolling out via Google Play.
- Chrome 159.0.8154.18 for Android released to limited users on November 18 with broader rollout planned.
- Out-of-bounds write in GPU can corrupt memory or allow malicious code execution through graphics rendering.
What is affected?
- Chrome Stable channel for Windows, Mac, and Linux before version 158.0.8127.36/.37
- Chrome for Android before version 158.0.8127.42
Summarised by SecOraLens from Malwarebytes Labs. Always read the original source before acting. How SecOraLens verifies advisories.
What to do next
Brief your board. Brief your team.
Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.
