Microsoft Edge 135 · Version Status
Microsoft Edge 135 End of Life Date
Microsoft Edge 135 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (learn.microsoft.com); the source of each date is on the product page.
⚠
Microsoft Edge 135 is past end of life. This version no longer receives security patches. 542 days past EOL — migrate to a supported version immediately.
EOL Date
May 1, 2025
542 days past EOL
Latest Release
135
Standard release
Release Date
Apr 3, 2025
Microsoft Edge 135 series
Where these dates come from
End of lifeMay 1, 2025Vendor's own page, read by our adapter · learn.microsoft.com · checked Oct 16, 2026high · 2 sources agree End of active supportMay 1, 2025Our catalog, built from the vendor pages · learn.microsoft.commedium · 1 source agrees ReleaseApr 3, 2025Vendor's own page, read by our adapter · learn.microsoft.com · checked Oct 16, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Microsoft Edge 135 was released on April 3, 2025 and support ended on May 1, 2025 — a supported lifespan of 28 days, in line with the 28 days median for Microsoft Edge releases. It was not an LTS release; Microsoft Edge reserves longer patch windows for its LTS versions. It has been past its end-of-life date for 1 year and 6 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 135 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. 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 135 end of life mean?
When Microsoft Edge 135 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Microsoft Edge 135 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 135 reach end of life?
Microsoft Edge 135 reached end of life on May 1, 2025. This version is no longer receiving security patches.
Is Microsoft Edge 135 still supported?
No. Microsoft Edge 135 reached end of life on May 1, 2025 and is no longer receiving security patches.
What should I upgrade to from Microsoft Edge 135?
What are the security risks of running Microsoft Edge 135 past EOL?
Since Microsoft Edge 135 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Microsoft Edge should migrate immediately or implement compensating controls.