What happened
The Stable channel has been updated to 152.0.7977.75/.76 for Windows and Mac and 152.0.7977.75 for Linux, which will roll out over the coming days/weeks.
Reported by Google on 2026-06-10 [N/A][546260492] Critical CVE-2026-84352: Use after free in WebGL.
What is verified
Reported by Google on 2026-08-14 [N/A][498839176] High CVE-2026-84354: Incorrect authorization in FileSystem.
Reported by Google on 2026-04-02 [N/A][514078656] High CVE-2026-84359: Information leak in Skia.
Reported by Google on 2026-05-17 [N/A][523208474] High CVE-2026-84357: Improper input validation in Omnibox.
Why it matters
A confirmed cyber incident can create secondary risk long after the initial intrusion. Stolen account data, contact information, or business records may be reused for phishing, credential attacks, identity fraud, or targeted social engineering. The source-backed facts above describe the incident; the downstream risk depends on what information was actually exposed.
What you should do
If you are notified that your information or account was affected, follow the organization’s incident instructions first. Change reused passwords, enable multifactor authentication, watch for targeted phishing, review security alerts and account sessions, and monitor financial or identity activity when sensitive personal information may have been involved.