
"The vulnerability received a high CVSS score of 8.8 and affects Chrome's V8 JavaScript engine. Security researcher Shaheen Fazim reported the use-after-free vulnerability. The issue lies in an iterator invalidation bug in CSSFontFeatureValuesMap, Chrome's implementation of CSS font feature values. Successful exploitation could allow attackers to cause browser crashes, rendering issues, data corruption, or other undefined behavior. Despite the patch, Google points to remaining work. So it may be a temporary fix, or related issues may still need to be addressed."
"Google has fixed the vulnerability for users in the Stable Desktop channel. New versions will be rolled out to Windows, macOS (145.0.7632.75/76), and Linux users (144.0.7559.75) worldwide in the coming days or weeks. Users who do not want to update manually can also have Chrome automatically check for updates via chrome://settings/help. The browser will install the update on the next restart."
"Although Google found evidence of attackers exploiting this zero-day flaw in the wild, the company did not share additional details about these incidents. "Access to bug details and links may be kept restricted until a majority of users are updated with a fix," the statement said. This is the first actively exploited Chrome security vulnerability to be patched since the beginning of 2026. Last year, Google addressed a total of eight zero-days that were exploited in the wild."
A use-after-free vulnerability with a CVSS score of 8.8 affects Chrome's V8 JavaScript engine. The root cause is an iterator invalidation bug in CSSFontFeatureValuesMap, Chrome's implementation of CSS font feature values. Exploitation can cause browser crashes, rendering problems, data corruption, or other undefined behavior. Google has issued patches for the Stable Desktop channel, with updates rolling out to Windows, macOS (145.0.7632.75/76) and Linux (144.0.7559.75). Chrome can check for updates via chrome://settings/help and will install the update after restart. Evidence shows in-the-wild exploitation; access to detailed bug information may remain restricted until most users update. Related issues may still require further fixes.
Read at Techzine Global
Unable to calculate read time
Collection
[
|
...
]