Google has rolled out Chrome 145, a version that finally ties the browser to Google Wallet for seamless autofill of payment and shipping details. Alongside this productivity-focused feature, the update patches 11 security flaws—including high-risk buffer overflow and CSS use-after-free bugs—though no active exploitation has been reported. The release also arrives a week later than originally scheduled, without an explanation from Google.

The new autofill integration works when users are signed into Chrome, pulling stored credit cards, addresses, and other payment information directly from Google Wallet. To enable it, navigate to Settings > Autofill and passwords > Enhanced autofill—a setting that promises faster checkout processes by eliminating manual data entry. Google highlights the feature on the browser’s What’s New tab, emphasizing how it streamlines transactions for logged-in users.

Security remains a priority in this update. Among the 11 fixed vulnerabilities

  • A high-risk buffer overflow in the codecs component (CVE-2026-2314).
  • A CSS use-after-free vulnerability (CVE-2026-2313), previously reported in December.
  • An inappropriate implementation in WebGPU (CVE-2026-2315), also classified as high risk.
  • Six medium-risk flaws and two low-risk issues, most involving memory corruption or improper data handling.

Google discovered three of the vulnerabilities internally, while external researchers reported the rest. Despite the severity of some flaws, none are known to be actively exploited in the wild. The delay in releasing Chrome 145—originally planned for last week—remains unexplained, though Google typically pushes updates automatically or via Help > About Google Chrome in the browser menu.

The update applies to Windows (versions 145.0.7632.45/46), macOS (145.0.7632.45), and Linux (145.0.7632.45). Chrome for Android (145.0.7632.45) and iOS (145.0.7632.55) also receive the same security fixes. Meanwhile, the Extended Stable Channel for Windows and macOS remains on Chromium 144.0.7559.173.

Looking ahead, Chrome 146 is expected in early March, with further refinements likely on the horizon. For now, users should ensure their browser is updated—either by waiting for the automatic prompt or manually checking for updates—while keeping an eye on Google’s security transparency reports for deeper technical details.