Chrome 158 Fixes 204 Vulnerabilities, Including Critical Code Execution Flaws

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Google began rolling out Chrome 158 to Windows, macOS, and Linux on November 17, 2026, with 204 security fixes. The desktop release notes list six critical memory bugs that could lead to code execution.

However, Google did not spell out the impact of each flaw. The patched builds are 158.0.8127.36 for Linux and 158.0.8127.36 or 158.0.8127.37 for Windows and macOS. Google said the update would reach users over the coming days and weeks.

Three critical flaws are use-after-free bugs. They affect WebView (CVE-2026-130963), garbage collection (CVE-2026-131008), and WebAudio (CVE-2026-130975).

A use-after-free happens when software keeps using memory after releasing it. That can crash a browser process or corrupt data. In some cases, this kind of memory error can let an attacker run code inside the affected process. That is not the same as gaining control of the entire device.

The other three critical flaws affect graphics and media processing. CVE-2026-131031 is an out-of-bounds write in the GPU component, while CVE-2026-131054 is the same type of bug in ANGLE, a graphics layer Chrome uses.

CVE-2026-131060 is a buffer overflow in Media. Both error types can cause Chrome to write beyond the memory set aside for data, potentially overwriting nearby information.

Google reported the WebView and ANGLE flaws. Xinyang Ge reported the other four critical issues, and Google credited Anthropic’s Claude with assisting on the GPU and Media reports.

Chrome 158 Fixes 204 Vulnerabilities

The release notes do not say whether any of the six were used in attacks or whether any could break out of Chrome’s sandbox, which limits what browser processes can access.

Critical Flaws :

CVE Severity Component Vulnerability Researcher credit
CVE-2026-130963 Critical WebView Use-after-free Google
CVE-2026-131031 Critical GPU Out-of-bounds write Xinyang Ge (Anthropic), assisted by Claude
CVE-2026-131060 Critical Media Buffer overflow Xinyang Ge (Anthropic), assisted by Claude
CVE-2026-131008 Critical GarbageCollection Use-after-free Xinyang Ge
CVE-2026-131054 Critical ANGLE Out-of-bounds write Google
CVE-2026-130975 Critical WebAudio Use-after-free Xinyang Ge (Anthropic)

The update fixes high-severity bugs in V8, Chrome’s JavaScript engine, as well as in Autofill, extensions, and downloads. Not all of the fixes address memory errors. Some correct permission checks were missing or applied incorrectly.

Google listed a $4,000 reward for Arni Hardarson of Neonix Security for reporting CVE-2026-130910, a high-severity failure in an ANGLE protection mechanism.

The release follows Chrome 157’s launch, which included 213 security fixes, and a separate November patch for a Chrome zero-day already used in attacks. Unlike that zero-day notice, Google’s Chrome 158 announcement does not flag active exploitation.

The company says it may restrict access to bug reports until most users have installed the fix, or keep reports closed longer if other projects still use an affected third-party library.

On Windows or macOS, open Chrome’s three-dot menu and go to Help, then About Google Chrome. The page checks for updates. When the download finishes, select Relaunch.

Linux users who installed Chrome through their distribution’s package manager should check for the update there, then restart the browser. After restarting, return to About Google Chrome and confirm that it shows the patched build for your platform or a newer version.

For IT teams, the rollout announcement is not proof that every managed device has installed the update. Check which Chrome version is running across the fleet, and follow up on devices that downloaded the patch but are still waiting for a browser restart.

Users who do not see Chrome 158 yet should check again as the rollout reaches their devices. The restart is what puts the new version into use.

Give your SOC the alert context on the latest threats to stop incidents quickly -> Integrate Threat Intel from 16K SOCs

The post Chrome 158 Fixes 204 Vulnerabilities, Including Critical Code Execution Flaws appeared first on Cyber Security News.