Security updates

Chrome update fixes MediaStream memory corruption

Google's October 29 Chrome update includes 21 security fixes, including CVE-2026-76024, a MediaStream memory-corruption issue.[1][2]

Fix. Update desktop Chrome Stable or Extended Stable to the fixed 156.0.8078.79/.80 builds for Windows and macOS, or 156.0.8078.79 on Linux, or a newer version, and relaunch to apply the update.[1][3][4]

Versions, remediation & sources
Affected systems & conditions
The Chrome CNA lists Chrome before 156.0.8078.79 as affected. It says a crafted HTML page could potentially read memory inside the sandbox; this record alone does not establish remote code execution or a sandbox escape.[2]
Remediation
Update desktop Chrome Stable or Extended Stable to the fixed 156.0.8078.79/.80 builds for Windows and macOS, or 156.0.8078.79 on Linux, or a newer version, and relaunch to apply the update. Google also announced Android 156.0.8078.79, with the same security fixes as the corresponding desktop release unless noted otherwise; update Android separately.[1][3][4]
Evidence at review time
Google's release note does not report in-the-wild exploitation of this issue. The CVE record includes CISA ADP's October 30 assessment of exploitation as none; that assessment is not proof that attacks cannot occur.[1][2]
Related context
This entry covers the October 29 MediaStream disclosure and is not a claim that this CVE is part of Anthropic's separately described Chrome exploit chain.[1][2][5]
Vendor severity
Google rates CVE-2026-76024 Critical. CISA ADP assigns the same CVE CVSS v3.1 6.5, Medium, with user interaction required; these are different severity assessments.[1][2]
Referenced CVEs