Chrome 145 Patches 11 Vulnerabilities
Source SecurityWeek
Rated by Threat Radar
Data as of 16 Feb 2026, 13:39 UTC
What to do
AI-suggested
European organizations should implement a robust patch management process to ensure all Chrome installations are updated to version 145 or later without delay. Automated update mechanisms should be enabled where possible to reduce the window of exposure. IT teams must verify Chrome versions across all endpoints and remediate any outdated installations. Network security controls such as web filtering and intrusion detection systems should be tuned to detect anomalous browser behavior indicative of exploitation attempts. Endpoint protection solutions should be updated to recognize exploit techniques targeting browsers. User awareness training should emphasize the importance of applying updates and recognizing phishing attempts that could deliver exploit payloads. Organizations should also consider isolating high-risk browsing activities in sandboxed environments or virtual machines to limit potential damage. Regular security audits and vulnerability assessments can help identify unpatched systems. Finally, monitoring threat intelligence feeds for emerging exploit information related to these vulnerabilities will enable proactive defense adjustments.
Description
Three of the security defects are high-severity flaws, two of which were found and reported by Google. The post Chrome 145 Patches 11 Vulnerabilities appeared first on SecurityWeek .