Google has released the 153.0.8010.52 update for the desktop version of Chrome. The release comes as 153.0.8010.52/.53 on Windows and macOS, and 153.0.8010.52 on Linux, and includes 16 security fixes. The package will roll out to all users over the next few days.
Critical fixes in PDF files and the graphics layer
The most notable item on the list is CVE-2026-93382, fixed in the PDFium library. The use-after-free flaw opens the door to remote code execution via a crafted HTML page; its CVSS score in the NVD record is 8.8, meaning high. The vulnerability was reported by researcher Huynh Dinh Vu, known as WinD39. A buffer overflow in the same library was also closed: CVE-2026-93381.
Of the two vulnerabilities marked critical, one is a buffer overflow in WebGL (CVE-2026-93372), and the other is a use-after-free flaw in the graphics layer Dawn (CVE-2026-93374). Google lists these two records with the highest severity rating.
Issues in the browser engine and extensions
A type confusion in the V8 JavaScript engine (CVE-2026-93377), a state validation error in Skia (CVE-2026-93387), an authorization error in ORB (CVE-2026-93379), and a reference resolution issue in the Tracing component (CVE-2026-93375) were also closed with high severity. CVE-2026-93373 on the extensions side, meanwhile, allowed code execution outside the sandbox via a crafted extension.
Seven medium- and low-severity issues were also fixed in the same package. Among them are a race condition in FileSystem (CVE-2026-93380), server-side request forgery in Omnibox (CVE-2026-93384), information leaks in the permissions and Paint components, and an out-of-bounds read in DataTransfer (CVE-2026-93376).
How to update your browser
Chrome updates itself automatically in the background, but if the browser hasn’t been closed for a long time, the new version doesn’t take effect. You can open Help > About Chrome from the menu and check the version number; if the update is ready, a restart prompt appears. On corporate computers, the update schedule is managed by the IT team.
Google keeps bug details and links restricted until most users have moved to the new version. For this reason, some bug records in the list are temporarily inaccessible.
Source: Chrome Releases · NVD

Share your experience
Bir sorunun, farklı bir çözümün veya eklemek istediğin bir notun var mı? Giriş yapmadan da yazabilirsin.