Chrome 142 Released With Fix for 20 Vulnerabilities that Allows Malicious Code Execution
\n \t
\n
<\/BR>
\n
\n \t
\n
<\/BR><\/p>\n
Google has officially promoted Chrome 142 to the stable channel, delivering critical security updates for Windows, Mac, and Linux users. <\/p>\n
The rollout begins immediately and will continue over the next few days or weeks, ensuring widespread protection against newly discovered threats. <\/p>\n
This version addresses 20 vulnerabilities<\/a>, many of which could enable attackers to execute malicious code remotely, potentially compromising user data and system integrity.<\/p>\n The update underscores Google\u2019s commitment to rapid response in the face of evolving browser-based attacks.<\/p>\n Chrome 142.0.7444.59 for Linux, 142.0.7444.59\/60 for Windows, and 142.0.7444.60 for Mac incorporate a range of fixes and performance improvements. <\/p>\n Detailed change logs are available through Chromium\u2019s source repository, highlighting enhancements in rendering, stability, and user interface. <\/p>\n While full details on new features will appear in upcoming posts on the Chrome and Chromium blogs, the immediate priority is bolstering defenses against exploitation attempts. <\/p>\n Security experts recommend users enable automatic updates to mitigate risks promptly, as unpatched browsers remain prime targets for cybercriminals.<\/p>\n The update addresses a wide range of vulnerabilities, including 20 security patches. Details about the bugs will initially remain confidential to allow for global deployment and to prevent facilitating active exploits.<\/p>\n Several fixes arise from external researchers, earning bounties under Google\u2019s Vulnerability Reward Program<\/a>, while others result from internal audits and fuzzing tools like AddressSanitizer and libFuzzer.<\/p>\n High-severity issues dominate, particularly in the V8 JavaScript engine, where type confusion, race conditions, and inappropriate implementations could lead to arbitrary code execution. <\/p>\n Media handling and extensions also receive attention, closing gaps that might allow unauthorized access or policy bypasses. Lower-severity fixes address UI inconsistencies and storage races, preventing subtle but persistent risks.<\/p>\n For a breakdown of key externally reported vulnerabilities, see the table below:<\/p>\n\nChrome 142 Released<\/strong> \u2013 Fix for 20 Vulnerabilities<\/strong>
\n<\/h2>\n