Chrome security patch fixes 16 unique bugs in the app; To look

Google Chrome’s latest update fixes 16 unique security issues. Some vulnerabilities also affect Chromium-based browsers such as Opera and Microsoft Edge.

According to the Common Vulnerabilities and Exposures list, issues are categorized by a severity level ranging from low to high. To: fixes pushed to Chrome 132.

The holes addressed in the security patch include out-of-bounds memory accesses, improper resource practices, and more.

Check out the list below Fixed loopholes discovered by third-party researchers and associated cash rewards (also converted to Realis):

• CVE-2025-0448 (US$ 1 thousand – R$ 6,023): Improper implementation of compositing;
• CVE-2025-0447 (US$ 1 thousand – R$ 6,023): Improper implementation of navigation;
• CVE-2025-0446 ($1k – R$6,023): Improper implementation in extensions;
• CVE-2025-0443 ($1,000 – $6,023): Insufficient data validation in extensions;
• CVE-2025-0442 (US$ 2 thousand – R$ 12,046): Improper practice in payments;
• CVE-2025-0441 (US$ 2 thousand – R$ 12,046): Improper implementation in Fenced Frameworks;
• CVE-2025-044 (US$ 5 thousand – R$ 30,115): Improper implementation in full screen;
• CVE-2025-0439 ($5k – R$30,115): Race in Frames;
• CVE-2025-0438 (Not yet disclosed) heap buffer overflow;
• CVE-2025-0437 ($2,000 – R$12,046): Out-of-bounds read in Metrics;
• CVE-2025-0436 ($3,000 – R$18,069): Integer overflow in Skia;
• CVE-2025-0435 (US$ 7 thousand – R$ 42,161): Improper implementation of navigation;
• CVE-2025-0434 ($7k – R$
• 42.161): Out-of-bounds memory access in V8.

Fixes are distributed via automatic update to all devices running Chrome 132. On Windows and Mac, the package is identified by the number 132.0.6834.83/84; On Linux it is 132.0.6834.83.

To check if there are any pending updates, click on the menu in the upper right corner of the screen, Help > About Chrome. In this section, the application will manually scan for updates.