Chrome patch fixes 26 flaws
Google pushed a Chrome update that patches 26 vulnerabilities, including several remote‑code‑execution bugs—prompt patching is critical for school endpoints. Automating browser updates via your MDM and scheduling compliance checks will cut exposure windows. (cyberpress.org)
Chrome’s Stable channel was pushed to version 146.0.7680.153/154 for Windows and macOS and 146.0.7680.153 for Linux in the March update that contains the fixes. (vpncentral.com) Two actively exploited zero‑day CVEs in this wave are CVE‑2026‑3909 (Skia out‑of‑bounds write) and CVE‑2026‑3910 (V8), both assigned high severity and confirmed by Google as being used in the wild. (securityweek.com) The U.S. CISA added those Chrome flaws to its Known Exploited Vulnerabilities catalog on March 13, 2026, and federal agencies were given an operational mitigation window with a March 27, 2026 remediation target. (cisa.gov) Google’s advisory and vendor writeups list affected components beyond Skia and V8 — including WebGL, WebRTC, Blink/ANGLE, CSS, PDFium, the network stack and the Digital Credentials API — indicating multiple attack surfaces a browser update closes. (cyberpress.org) Chrome Enterprise documentation shows full feature releases ship about every six weeks while security/minor updates occur every 2–3 weeks, and recommends enforcing automatic updates via Group Policy/MDM rather than relying on end‑user restarts. (support.google.com) Admins can enforce Chrome auto‑updates in Intune by importing Google’s ADMX templates and setting Google Update policies (e.g., AutoUpdateCheckPeriodMinutes / UpdateDefault) to ensure devices check and accept updates on a policy schedule. (prajwaldesai.com) Proactive Remediation scripts or a one‑off PowerShell remediation deployed through Intune can force an immediate chrome.exe update check for segmented device groups (for example, separate profiles for each campus), simplifying patch drives for a single IT operator managing two sites. (hub.sivo.it.com)
