Google began rolling out Chrome 158 on Nov. 17 with 204 security fixes, including six critical vulnerabilities and 62 rated high. The desktop update is rolling out as versions 158.0.8127.36 and .37 for Windows and macOS, and 158.0.8127.36 for Linux.
The company did not report in-the-wild exploitation in its release notes.
Six critical vulnerabilities
The six critical vulnerabilities affect different browser components. They include three use-after-free flaws, two out-of-bounds write vulnerabilities, and one buffer overflow, all of which can result in memory corruption under certain conditions.
Use-after-free vulnerabilities occur when a program accesses memory that has already been released, potentially allowing an attacker to manipulate how the browser handles data.
The two out-of-bounds write flaws, meanwhile, could allow data to be written beyond its allocated memory space. At the same time, the buffer overflow can similarly cause excess data to overwrite neighboring memory.
These aren't just programming errors that can cause Chrome to crash. Depending on the circumstances and how they are exploited, memory corruption vulnerabilities can allow attackers to execute malicious code within an affected browser process.
The affected components include WebView, GarbageCollection, WebAudio, GPU, ANGLE, and Media — all components affecting different parts of the Chrome software.
Other vulnerabilities still matter
The remaining 198 fixes—spanning 62 high-, 82 medium-, and 54 low-severity flaws—are just as important to patch. High-severity bugs carry serious standalone risks, while lower-severity weaknesses are frequently chained together in multi-stage attacks, making the full update essential.
High-severity flaws are particularly worth watching because they can still expose users to significant security risks, even if they don't meet the threshold for critical classification.
Medium- and low-severity vulnerabilities also deserve attention, not necessarily because of their risk levels, but for what they can do when chained with other weaknesses.
Taken together, these fixes show why the update shouldn't be judged by its six critical flaws alone. The remaining vulnerabilities add to the number of weaknesses Chrome users could face if they keep running unpatched versions of the browser, making the entire security release worth installing.
AI and human researchers both contributed
AI is becoming an increasingly useful part of Google's Chrome security process, helping the company identify vulnerabilities and speed up the work involved in investigating and fixing them.
However, the latest release shows that human expertise remains just as relevant, with Google's internal security teams and external researchers also contributing to the findings. AI assistance was also credited with discovering some of the critical vulnerabilities.
Per SecurityWeek, Google has already paid out $11,000 in bug bounty rewards for five reported vulnerabilities, while another 36 reported findings are still awaiting reward decisions.
IT teams have some checklists to clear
Chrome generally downloads security updates automatically, but that doesn't mean every user receives and installs them as soon as Google releases them. Updates can remain pending for a while, leaving some users on vulnerable versions even after a fix becomes available.
If you use Chrome, type chrome://version into your browser's address bar to check the installed version. If it hasn't updated to the latest release, close Chrome completely and reopen it to apply the pending update. You can revisit the same page afterward to verify that the version has changed.
For IT teams managing fleets of devices, the responsibility extends beyond reminding employees to update their browsers. Administrators need to verify that Chrome 158 has reached managed devices, confirm that pending updates have been applied, and ensure employees are no longer running older, vulnerable versions.
With 204 vulnerabilities addressed in this release, leaving patches unapplied across an organization could expose many devices to weaknesses Google has already fixed.
Other news: The NSA’s classified internal communications network, NSANet, was reportedly down on Nov. 17, but US officials told CNN that backup networks could still carry urgent intelligence to the president.





