Edge 154.0.4258.62 security update: install and verify on your PC

If Microsoft Edge is the browser you actually use on a home Windows or Mac computer, check the version today. On October 5, 2026, Microsoft shipped Stable 154.0.4258.62 (Update 3 on the Edge 154 train). The Stable channel release notes list bug and performance fixes plus a security line that points at Microsoft’s Edge security update pages.

The same day’s Edge security release notes say Stable 154.0.4258.62 incorporates the latest security updates from the Chromium project. You do not need a CVE scavenger hunt. You need that build running, then a clean relaunch.

This is separate from Google Chrome. Updating Chrome does not update Edge. Updating Edge does not update Chrome. See our Chrome 154.0.8037.97 security note if Chrome is also on your machine.

What Microsoft shipped on October 5

From Microsoft’s Stable channel notes for Version 154.0.4258.62 (October 5, 2026):

Fixes: various bugs and performance issues
Security: Stable channel security updates (Microsoft’s security release notes page)

Microsoft’s security notes for that date name the Stable build explicitly and point readers at the Security Update Guide for Chromium ingest details. Microsoft often publishes Edge-specific CVE lists on bigger drops and shorter “incorporates Chromium security updates” notes on mid-cycle builds. Treat 154.0.4258.62 as the current Stable target until a newer minor shows up.

Extended Stable also moved the same day to 152.0.4191.119. Most home users are on normal Stable, not Extended Stable. If you never changed channels, you want the 154.0.4258.62 line.

Edge 154 itself landed as a major Stable release on September 24, 2026 at 154.0.4258.37, with feature notes about profile setup, Google account sign-in on Windows and macOS, password key-icon details, and the ongoing unload-event deprecation. Those features are nice. They are not a substitute for being on the October 5 security build.

Why mid-cycle Edge bumps matter

Browsers ship security packages between the big “new major version” headlines. Edge follows Chromium on a fast cadence. If edge://version still shows 154.0.4258.37, .48, or .53, you are behind the October 5 package even though you already “updated to Edge 154.”

Same habit every time:

Update
Fully quit and relaunch
Prove it with edge://version

Downloaded is not running. The version page is the receipt.

How to update and verify on a home PC or Mac

Open Microsoft Edge on the computer you browse with.
Check for updates:
- Windows / Linux: Menu (three dots) → Help and feedback → About Microsoft Edge.
- Mac: Edge menu → About Microsoft Edge.
Stay on that page until the download finishes and Edge offers a restart, or until it already shows 154.0.4258.62 (or a newer 154.0.4258.x if Microsoft ships one after this article).
Restart when prompted. Do not click Later and leave old windows open for hours.
If the version still looks old, fully quit Edge (every window). On Windows, confirm no leftover msedge.exe helpers in Task Manager. On Mac, use Edge → Quit Microsoft Edge. Open Edge again.
Type edge://version in the address bar. You want 154.0.4258.62 or newer on the same 154 train.
Repeat on other machines you use, including a laptop that sleeps with Edge still open and any shared family PC.

If About Edge says an update is coming but does not offer .62 yet, give Stable a day, then check again. Microsoft stages these.

Android and iOS Edge, separately

Desktop Edge updates do not patch the phone apps. Edge on Android and iOS updates through Google Play or the App Store on their own schedules. Microsoft’s security notes listed an Android Edge 154.0.4258.38 package on September 29, 2026. Check the store listing on your phone if that is how you browse, and open the app once after it updates so the new build actually launches.

Do this / don’t do that

Force About Microsoft Edge, relaunch, and confirm edge://version shows 154.0.4258.62 or newer.
Update Chrome, Firefox, Safari, and Brave on their own pages if you use them. Edge is only one browser.
Fully quit leftover Edge processes after an update prompt.
Treat mid-cycle security builds as “install today,” not “install when I remember on Sunday.”

Don’t

Do not stop at 154.0.4258.37 (or .48 / .53) because you already “did the Edge 154 update.”
Do not assume a Windows Update reboot alone refreshed Edge if edge://version is still old.
Do not invent exploit details for Chromium bugs that Microsoft has not listed on the Edge security page yet.
Do not download random “Edge offline installer” packs from third-party sites. Use Edge’s own About page or Microsoft’s download links.

Bottom line

Microsoft’s October 5, 2026 Stable update ships Edge 154.0.4258.62 with Chromium security ingest and assorted fixes (Stable channel notes, security release notes). On your own computer: open About Microsoft Edge, install, fully quit and relaunch, confirm edge://version. That is the whole job.

Image: Microsoft Edge logo on a white field (Microsoft Edge blog, blogs.windows.com).