Google just shipped a large round of Chrome security fixes, patching 37 vulnerabilities — seven of them rated critical — while Edge users are left waiting for Microsoft to deliver the same Chromium fixes on its side.
That gap is a familiar one. Chrome and Edge both run on the Chromium engine, so the underlying security work is shared, but the two browsers ship it on separate timelines. When Google releases a batch of fixes, Microsoft generally folds them into a later Edge build, and that rollout has not landed yet.
What actually changed in the Chrome security fixes
According to the summary of the update, Chrome’s patch cleared out 37 security flaws in total, with seven classified as critical severity. Critical vulnerabilities are the ones most likely to be actively exploited in the wild, so their inclusion marks this as a particularly notable release for the browser.
When a browser vendor ships dozens of fixes at once, it usually means security researchers had been digging into the codebase and turned up a wide range of problems — from memory-corruption bugs that can crash a page to deeper flaws that could allow code execution. The exact scope of each of the 37 issues isn’t detailed in the brief summary, but the critical count is the number worth paying attention to.
Why Edge users are still waiting
Edge is built on the same Chromium foundation as Chrome, which is why Microsoft typically adopts Google’s security patches — but not immediately. Microsoft runs its own testing and quality-assurance cycle before folding upstream fixes into an Edge release, and that process takes time.
As a result, Edge has historically trailed Chrome on security updates. In this case, the same set of Chromium fixes that reached Chrome has not yet been delivered to Edge, meaning anyone still running the browser is sitting on unpatched code that Chrome users no longer have.
This lag is worth noting because security updates aren’t just about new features — they close holes that attackers can walk through. Even if your browsing feels fine, an unpatched browser is still exposed to the same flaws Chrome just fixed.
What this means for you
If you use Chrome, the fix is already out — you just need to make sure you’ve installed it. If you prefer Edge, you’ll want to check for an update soon, since Microsoft hasn’t shipped the corresponding patch yet.
The practical takeaway is simple: don’t wait around for a browser to tell you it’s out of date. Both Chrome and Edge can update themselves in the background, but forcing a manual check now is the fastest way to close the gap, especially if you’re still on an older build.
How to get the fixes
For Chrome, open the browser’s menu and check for an update, or simply relaunch — most recent Chrome installs apply the patch automatically on the next restart. The browser will typically prompt you to restart once the new build is ready.
For Edge, head into the browser’s help and settings menu to look for an update. If Microsoft has already published the Chromium fixes into an Edge build, a manual check should pull it down. If not, you’ll need to wait for the next scheduled release.
One thing to keep in mind: automatic updates usually handle this for you, but if you manage a fleet of machines or prefer to stay on a specific build, you may need to time your updates deliberately to match Microsoft’s release cadence.
Why Chromium updates matter across the board
Because so many browsers — including Edge, and several others — run on Chromium, a single security release from Google can have a ripple effect across the whole ecosystem. That’s both a strength and a vulnerability: fixing a flaw in Chromium helps everyone, but a gap there can expose everyone at once.
This is exactly why security researchers keep scrutinizing the engine, and why vendors like Microsoft can’t afford to be too far behind. The current situation, with Chrome patched and Edge still catching up, is a reminder that “using a Chromium browser” doesn’t automatically mean “you’re protected” — you still have to be on the updated build.
The bottom line
Chrome security fixes are now in your hands if you’re on Chrome; the clock is simply ticking for Edge users. Check both browsers now rather than relying on a background update that may arrive days later.
Source: Neowin
Over to you: Are you sticking with Chrome for its faster security patches, or do you trust Edge to catch up?
You may also like
Mozilla Launches Firefox Enterprise to Challenge Microsoft Edge and Google Chrome in the Browser Market
Microsoft Forms Xbox Labs to Prototype AI-Inspired Game Remixes
Microsoft Decision-1: the new AI model that decides instead of writing
Microsoft Is Retiring Two AI App-Building Services in Favor of Copilot
