Microsoft Edge vulnerabilities: known CVEs & security history
Microsoft · Browser · 116 tracked CVEs · 1 actively exploited · updated October 2026 · what is a CVE? →
This is the full list of known vulnerabilities (CVEs) across all Microsoft Edge release lines — 116 in total, with 1 actively exploited in the wild. A CVE here doesn't mean your version is affected — check Microsoft Edge's current status and the safe version to run.
Known Microsoft Edge CVEs
Actively-exploited and most-severe first. Showing the top 80 of 116. Open any CVE for full details.
| CVE | Severity | CVSS | EPSS | Year |
|---|---|---|---|---|
| CVE-2025-14174⚡ exploited | high | 8.8 | 22% | 2025 |
| CVE-2026-58289 | critical | 9 | 2% | 2026 |
| CVE-2026-85893 | high | 8.8 | 1% | 2026 |
| CVE-2026-69486 | high | 8.8 | 1% | 2026 |
| CVE-2026-72984 | high | 8.8 | 0% | 2026 |
| CVE-2026-57981 | high | 8.8 | 1% | 2026 |
| CVE-2026-57974 | high | 8.8 | 1% | 2026 |
| CVE-2026-56645 | high | 8.8 | 1% | 2026 |
| CVE-2026-32208 | high | 8.8 | 1% | 2026 |
| CVE-2026-45495 | high | 8.8 | 1% | 2026 |
| CVE-2023-36787 | high | 8.8 | 2% | 2023 |
| CVE-2026-57983 | high | 8.7 | 1% | 2026 |
| CVE-2026-70341 | high | 8.5 | 1% | 2026 |
| CVE-2026-72970 | high | 8.3 | 1% | 2026 |
| CVE-2026-58596 | high | 8.3 | 1% | 2026 |
| CVE-2026-58281 | high | 8.3 | 1% | 2026 |
| CVE-2026-58295 | high | 8.3 | 1% | 2026 |
| CVE-2026-58288 | high | 8.3 | 1% | 2026 |
| CVE-2026-58287 | high | 8.3 | 1% | 2026 |
| CVE-2026-58285 | high | 8.3 | 1% | 2026 |
| CVE-2026-58284 | high | 8.3 | 1% | 2026 |
| CVE-2026-50521 | high | 8.3 | 1% | 2026 |
| CVE-2024-21399 | high | 8.3 | 1% | 2024 |
| CVE-2023-36741 | high | 8.3 | 2% | 2023 |
| CVE-2023-23374 | high | 8.3 | 1% | 2023 |
| CVE-2026-58525 | high | 8.2 | 1% | 2026 |
| CVE-2024-26192 | high | 8.2 | 2% | 2024 |
| CVE-2026-88097 | high | 8.1 | 0% | 2026 |
| CVE-2026-66318 | high | 8.1 | 0% | 2026 |
| CVE-2026-58293 | high | 8.1 | 1% | 2026 |
| CVE-2026-58286 | high | 8.1 | 0% | 2026 |
| CVE-2026-58283 | high | 8.1 | 0% | 2026 |
| CVE-2026-58282 | high | 8.1 | 0% | 2026 |
| CVE-2026-85892 | high | 7.8 | 0% | 2026 |
| CVE-2026-57985 | high | 7.6 | 1% | 2026 |
| CVE-2026-66315 | high | 7.5 | 1% | 2026 |
| CVE-2026-58299 | high | 7.5 | 0% | 2026 |
| CVE-2026-58294 | high | 7.5 | 1% | 2026 |
| CVE-2026-58292 | high | 7.5 | 0% | 2026 |
| CVE-2026-58290 | high | 7.5 | 0% | 2026 |
| CVE-2026-58276 | high | 7.5 | 1% | 2026 |
| CVE-2026-57992 | high | 7.5 | 1% | 2026 |
| CVE-2026-57986 | high | 7.5 | 1% | 2026 |
| CVE-2026-57984 | high | 7.5 | 1% | 2026 |
| CVE-2026-57975 | high | 7.5 | 1% | 2026 |
| CVE-2026-66321 | high | 7.4 | 1% | 2026 |
| CVE-2026-65802 | high | 7.4 | 1% | 2026 |
| CVE-2026-57990 | high | 7.4 | 1% | 2026 |
| CVE-2026-57989 | high | 7.4 | 0% | 2026 |
| CVE-2026-57993 | high | 7.4 | 1% | 2026 |
| CVE-2026-57991 | high | 7.4 | 1% | 2026 |
| CVE-2026-41107 | high | 7.4 | 1% | 2026 |
| CVE-2026-58298 | high | 7.2 | 0% | 2026 |
| CVE-2026-66322 | high | 7.1 | 0% | 2026 |
| CVE-2026-58297 | high | 7.1 | 1% | 2026 |
| CVE-2026-58296 | high | 7.1 | 1% | 2026 |
| CVE-2026-57988 | high | 7.1 | 1% | 2026 |
| CVE-2026-57977 | high | 7.1 | 1% | 2026 |
| CVE-2026-66313 | medium | 6.8 | 0% | 2026 |
| CVE-2026-58522 | medium | 6.8 | 0% | 2026 |
| CVE-2026-66324 | medium | 6.5 | 1% | 2026 |
| CVE-2026-66326 | medium | 6.5 | 1% | 2026 |
| CVE-2026-66314 | medium | 6.5 | 1% | 2026 |
| CVE-2026-66312 | medium | 6.5 | 1% | 2026 |
| CVE-2026-58523 | medium | 6.5 | 1% | 2026 |
| CVE-2026-57987 | medium | 6.5 | 1% | 2026 |
| CVE-2026-56646 | medium | 6.5 | 1% | 2026 |
| CVE-2026-45489 | medium | 6.5 | 1% | 2026 |
| CVE-2026-45173 | medium | 6.5 | 0% | 2026 |
| CVE-2026-42891 | medium | 6.5 | 0% | 2026 |
| CVE-2024-43496 | medium | 6.5 | 1% | 2024 |
| CVE-2024-43489 | medium | 6.5 | 1% | 2024 |
| CVE-2023-38157 | medium | 6.5 | 2% | 2023 |
| CVE-2021-38669 | medium | 6.4 | 3% | 2021 |
| CVE-2025-60711 | medium | 6.3 | 0% | 2025 |
| CVE-2021-36929 | medium | 6.3 | 3% | 2021 |
| CVE-2026-66311 | medium | 6.2 | 0% | 2026 |
| CVE-2026-58300 | medium | 6.2 | 0% | 2026 |
| CVE-2026-77490 | medium | 6.1 | 0% | 2026 |
| CVE-2026-66325 | medium | 6.1 | 0% | 2026 |
36 older / lower-severity CVEs not shown — see Microsoft Edge's full record.
Is my Microsoft Edge version affected?
The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.
Check your Microsoft Edge version → · Monitor Microsoft Edge for new CVEs →
Microsoft Edge vulnerabilities — frequently asked
How many known vulnerabilities does Microsoft Edge have?
IsItPatched tracks 116 CVEs for Microsoft Edge, 1 of which is actively exploited (CISA KEV). 1 is critical-severity and 57 high-severity. These span every release line — what matters is whether the version you run is affected.
Does Microsoft Edge have any actively-exploited vulnerabilities?
Yes — 1 Microsoft Edge CVE is in CISA's Known Exploited Vulnerabilities catalog, meaning it is confirmed exploited in the wild. Patch it as a priority.
What is the most severe Microsoft Edge vulnerability?
Among tracked issues, CVE-2025-14174 (HIGH, CVSS 8.8), which is actively exploited, ranks highest — a Out-of-bounds write weakness.
Is Microsoft Edge safe to use?
It depends on the version. The latest supported Microsoft Edge release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.
CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Microsoft Edge security status · Microsoft Edge end-of-life · actively-exploited CVEs. Always verify against Microsoft's advisories — see our disclaimer.