|
In the Chrome Releases blog post, Krishna Govind provided the scant details that Google revealed about the zero-day vulnerability (CVE-2025-6554), which Google classifies as high risk. It's a classic issue that crops up practically every month: a type mix-up in the V8 JavaScript engine. The discoverer of the vulnerability is also no stranger: Clément Lecigne from Google's Threat Analysis Group (TAG), who has discovered zero-day vulnerabilities in Chrome several times before.
Lecigne discovered the problem on June 25th. Then, on June 26th, Google sent a configuration change to all Chrome installations on the Stable Channel of all platforms to mitigate the problem. The update now available should take care of the rest. A week ago, Google released the new major version of Chrome 138, which addressed 11 security flaws.
As a rule, Chrome updates itself automatically when a new version is available. You can manually initiate the update check using the menu and navigating to Help About Google Chrome. Go
|
|
According to Windows Latest, the issues don't just stop at the popular productivity shortcut either. Other issues include mouse cursor lag, screen resolution issues, and difficulties adjusting volume.
KB5060829 is a preview update, which means it's optional to install and allows you to try out new features and improvements ahead of the general release. However, preview updates can have problems like this, so you shouldn't blindly install them on mission-critical PCs.
The update is supposed to be rolled out to all users in two weeks, so hopefully Microsoft fixes these issues in time. Until then, you should hold off on installing update KB5060829 to avoid these issues. Meanwhile, if you're affected, try rolling back the problematic update.
|
RELATED ARTICLES | | |
|
