Google Chrome Releases: Stable Channel Update for Desktop
Google Chrome Releases has published a new security advisory. Here is a summary and what to do.
Key points
- New advisory from Google Chrome Releases.
- Review affected versions in the advisory.
- Apply updates promptly.
Google Chrome Releases published a security advisory titled “Stable Channel Update for Desktop”.
At a glance
- Publisher
- Google Chrome Releases
- CVEs
- See advisory
What the advisory says
The Chrome team is delighted to announce the promotion of Chrome 156 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks. Chrome 156.0.8078.47 (Linux) 156.0.8078.47/.48 Windows/Mac contains a number of fixes and improvements -- a list of changes is available in the log . Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 156. Security Fixes and Rewards Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed. This update includes 353 security fixes. Please see the Chrome Security Page for more information. [N/A][ 569165786 ] Critical CVE-2026-113341: Memory corruption in Skia. Reported by Google on 2026-1
What should you do?
- Read the full vendor advisory linked below and confirm whether you run affected versions.
- Schedule the recommended update, prioritising internet-facing systems.
- Watch for exploitation reports; unpatched edge devices are frequent targets.
What to do and how to stay safe: Google Chrome Releases
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
