Current update alert
Chrome 151 includes important security fixes
Google has released Chrome 151 to the Stable channel and security reporting has highlighted critical vulnerabilities addressed by the update. Rollout versions can differ by operating system and may be superseded by a newer maintenance release, so verify the current fixed build against Google's live release channel rather than relying on a version copied into an older article.
Action now
Confirm that Chrome is updating, ask users to relaunch where required, and identify devices that remain on an older build. Prioritise administrators, finance teams, staff handling sensitive care information and devices used for privileged cloud access.
Why browsers matter
A browser is part of the security boundary
Browsers routinely process untrusted websites, documents, scripts, media and authentication sessions. They also provide access to email, collaboration platforms, finance systems and cloud administration. A vulnerable or persistently outdated browser can therefore undermine otherwise strong identity and endpoint controls.
Frequent releases are normal. The sustainable response is not a new emergency project for every version, but a repeatable process that makes exceptions and failures visible.
Individual devices
Verify an installation manually
Open the update page
In Chrome, visit chrome://settings/help. Chrome checks for an available update and displays the installed version.
Relaunch when prompted
An update may be downloaded but not active until every Chrome window is closed and the browser is relaunched. Preserve important work before restarting.
Compare with the live release
Check Google's Chrome Releases channel for the latest Stable version for the device's operating system. A newer maintenance build should take precedence over the original Chrome 151 release.
Check policy when updates fail
Use chrome://policy to identify update restrictions on managed devices. Chrome 148 and later also provides chrome://updater for updater status, installed applications, policy and event information.
Read-only Windows check
Confirm the locally installed executable version
This PowerShell example checks common system-wide and per-user installation paths. It only reads file-version information and makes no changes.
$chromePaths = @(
"$env:ProgramFiles\Google\Chrome\Application\chrome.exe"
"${env:ProgramFiles(x86)}\Google\Chrome\Application\chrome.exe"
"$env:LOCALAPPDATA\Google\Chrome\Application\chrome.exe"
) | Select-Object -Unique
$results = foreach ($chromePath in $chromePaths) {
if (Test-Path -LiteralPath $chromePath) {
$file = Get-Item -LiteralPath $chromePath
[pscustomobject]@{
ComputerName = $env:COMPUTERNAME
Version = $file.VersionInfo.ProductVersion
InstallPath = $file.FullName
}
}
}
if ($results) {
$results | Format-Table -AutoSize
} else {
Write-Warning 'Chrome was not found in the common installation paths.'
}What this does not prove
A file version alone does not confirm that every running Chrome process has loaded the update, that all user-scoped installations were discovered, or that unmanaged devices are safe. Treat it as one piece of evidence.
Organisation-wide verification
Move from individual checks to measurable coverage
Establish inventory
Use endpoint-management, software-inventory or Chrome Enterprise reporting to identify installed versions and devices that have stopped reporting.
Allow timely updates
Review Google Update policy and remove unnecessary version pins or disabled-update settings. Document any temporary exception and expiry date.
Separate download from adoption
Measure pending restarts or stale browser sessions where tooling permits. Communicate a relaunch deadline for important security releases.
Include unmanaged access
Decide how personal and unmanaged devices may access sensitive systems. Browser patching should form part of the wider device-trust decision.
Operational workflow
A proportionate browser-update process
| Stage | Practical action |
|---|---|
| Monitor | Follow vendor release channels and trusted security reporting. Record the affected product, fixed versions, severity and exploitation status. |
| Assess | Confirm whether the browser is present, where it is used and whether exposed groups or privileged users need faster action. |
| Deploy | Allow automatic updating or use existing management tooling. Test critical extensions and workflows without creating an unnecessary general delay. |
| Verify | Measure the percentage at or above the required version, devices awaiting restart, failures and devices absent from inventory. |
| Escalate | For known exploitation or critical risk, shorten deadlines, contact affected users directly and restrict high-risk access where proportionate. |
| Evidence | Retain the vendor notice, decision record, deployment status, exceptions, completion report and lessons learned. |
RACF-CC context
Connect patching to endpoint assurance
This process supports RACF-CC Domain 2 by improving device visibility and supported software, Domain 4 by turning vulnerability information into prioritised remediation, Domain 6 through reliable inventory and alerting, and Domain 8 through ownership, exceptions and evidence.
Minimum viable outcome
The organisation can identify its managed browsers, confirm the current vendor-supported version, show how quickly important updates are adopted, and name every unresolved exception with an owner and review date.
Sources and live guidance
Use the vendor release channel as the authority
- Google Chrome Releases: live Stable channel updates
- Chrome for Developers: Chrome 151 release notes
- Google: Manage Chrome updates on Windows
- Google: Maintain Chrome updates on Windows and Mac
- SecurityWeek: Critical vulnerabilities patched with Chrome 151
Vendor versions and rollout details change frequently. Confirm the live release information before setting a compliance threshold or communicating a required version.
Voluntary support
Found this useful? Support Trends4You
Trends4You's practical guides, RACF-CC resources and downloadable tools are provided free of charge. If they've helped you or your organisation, you can support the time and hosting that keeps them freely available.
Support is optional, handled securely by Stripe and does not provide additional access.