Microsoft Edge 132 · Version Status
Microsoft Edge 132 End of Life Date
Microsoft Edge 132 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Microsoft Edge 132 is past end of life. This version no longer receives security patches. 580 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 6, 2025
580 days past EOL
Latest Release
132
LTS release
Release Date
Jan 17, 2025
Microsoft Edge 132 series
Extended Support
Mar 6, 2025
Extended support · ended
Lifecycle detail
Microsoft Edge 132 was released on January 17, 2025 and support ended on February 6, 2025 — a supported lifespan of 20 days, shorter than the 28 days median for Microsoft Edge LTS releases. It was a long-term support (LTS) release, so it received a longer patch window than the interim releases around it. It has been without security patches for 1 year and 7 months. 19 newer Microsoft Edge releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Microsoft Edge 132 support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Microsoft Edge Versions
| Version | Latest | EOL Date | Status |
|---|
| 88 |
88 |
Mar 8, 2021 |
EOL |
| 89 |
89 |
Apr 15, 2021 |
EOL |
| 90 |
90 |
May 27, 2021 |
EOL |
| 91 |
91 |
Jul 22, 2021 |
EOL |
| 92 |
92 |
Sep 2, 2021 |
EOL |
| 93 |
93 |
Sep 24, 2021 |
EOL |
| 94 LTS |
94 |
Oct 21, 2021 |
EOL |
| 95 |
95 |
Nov 19, 2021 |
EOL |
What does Microsoft Edge 132 end of life mean?
When Microsoft Edge 132 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Microsoft Edge 132 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Microsoft Edge 132 reach end of life?
Microsoft Edge 132 reached end of life on February 6, 2025. This version is no longer receiving security patches.
Is Microsoft Edge 132 still supported?
No. Microsoft Edge 132 reached end of life on February 6, 2025 and is no longer receiving security patches.
What should I upgrade to from Microsoft Edge 132?
What are the security risks of running Microsoft Edge 132 past EOL?
When Microsoft Edge 132 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Microsoft Edge should migrate immediately or implement compensating controls.