microsoft edge chromium
productUScpe:2.3:a:microsoft:edge_chromium:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
10critical66high85medium2low
updated 2026-10-27
| ID | severity CVSS base severity and score (0–10). | EPSS FIRST.org probability this is exploited in the next 30 days, with its percentile rank among all CVEs. | exploitable On CISA's Known Exploited Vulnerabilities list, or a public exploit is on file. | patched Whether a fixed version is on file for an affecting range. | published | affected |
|---|
| CVE-2023-4863US | high8.8OT critical | 100.0% (100th) | KEV | ✓116.0.1938.81 | 2023-09-12 | < 116.0.1938.81 |
| CVE-2025-14174US | —OT critical | 55.3% (99th) | KEV | ✓143.0.3650.80 | 2025-12-12 | < 143.0.3650.80 |
| CVE-2023-4762US | high8.8OT critical | 41.4% (99th) | KEV | ✓116.0.1938.76 | 2023-09-05 | < 116.0.1938.76 |
| CVE-2024-7965US | high8.8OT critical | 18.5% (97th) | KEV | ✓128.0.2739.42 | 2024-08-21 | < 128.0.2739.42 |
| CVE-2025-6554US | —OT critical | 14.1% (97th) | KEV | ✗no fix | 2025-06-30 | ≤ vers:unknown/<138.0.3351.65 |
| CVE-2025-5419US | —OT critical | 7.82% (95th) | KEV | ✓137.0.3296.62 | 2025-06-03 | < 137.0.3296.62 |
| CVE-2023-5217US | high8.8OT critical | 49.0% (99th) | KEV | ✗no fix | 2023-09-28 | 2 versions |
| CVE-2020-16009US | high8.8OT critical | 48.3% (99th) | KEV | ✓86.0.4240.183 | 2020-11-03 | < 86.0.4240.183 |
| CVE-2022-4135US | critical9.6OT critical | 31.9% (98th) | KEV | ✓107.0.5304.150 | 2022-11-25 | < 107.0.5304.150 |
| CVE-2023-6345US | critical9.6OT critical | 16.5% (97th) | KEV | ✓119.0.2151.97 | 2023-11-29 | < 119.0.2151.97 |
| CVE-2023-6702US | high8.8 | 44.3% (99th) | Exploit | ✓120.0.2210.77 | 2023-12-14 | < 120.0.2210.77 |
| CVE-2024-21388US | — | 32.0% (98th) | Exploit | ✓121.0.2277.83 | 2024-01-30 | < 121.0.2277.83 |
| CVE-2021-21123US | medium6.5 | 10.9% (96th) | Exploit | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2023-33145US | — | 8.62% (95th) | Exploit | ✓114.0.1823.51 | 2023-06-14 | < 114.0.1823.51 |
| CVE-2025-49741US | high7.5 | 3.91% (90th) | Exploit | ✓135.0.3179.98 | 2025-07-01 | 2 versions |
| CVE-2023-24892US | — | 3.52% (89th) | Exploit | ✓111.0.1661.41 | 2023-03-14 | < 111.0.1661.41 |
| CVE-2022-21970US | high8.3 | 2.54% (85th) | Exploit | ✓97.0.1072.55 | 2022-01-11 | < 97.0.1072.55 |
| CVE-2026-58289US | high8.3 | 1.99% (81st) | Exploit | ✓150.0.4078.48 | 2026-07-03 | < 150.0.4078.48 |
| CVE-2024-30056US | medium5.4 | 1.55% (75th) | Exploit | ✓124.0.2478.109 | 2024-05-25 | < 124.0.2478.109 |
| CVE-2021-21132US | critical9.6 | 23.4% (98th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21135US | medium6.5 | 19.2% (97th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21118US | high8.8 | 16.8% (97th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21157US | high8.8 | 9.46% (95th) | — | ✓88.0.4324.182 | 2021-02-22 | < 88.0.4324.182 |
| CVE-2021-21126US | medium6.5 | 8.73% (95th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21125US | high8.1 | 8.08% (95th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21124US | critical9.6 | 7.85% (95th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21131US | medium6.5 | 7.65% (95th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21122US | high8.8 | 7.01% (94th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21120US | high8.8 | 6.88% (94th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21119US | high8.8 | 6.83% (94th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21128US | high8.8 | 6.51% (94th) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21121US | critical9.6 | 6.19% (93rd) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21137US | medium6.5 | 5.92% (93rd) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21127US | high8.8 | 5.88% (93rd) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-30615US | medium6.5 | 5.59% (93rd) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
| CVE-2021-21130US | medium6.5 | 5.44% (93rd) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21129US | medium6.5 | 5.44% (93rd) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21134US | medium6.5 | 5.04% (92nd) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-21139US | medium6.5 | 4.74% (92nd) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-30614US | high8.8 | 4.46% (91st) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
| CVE-2021-21136US | medium6.5 | 4.17% (91st) | — | ✓88.0.705.50 | 2021-02-09 | < 88.0.705.50 |
| CVE-2021-30616US | high8.8 | 4.14% (91st) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
| CVE-2021-30609US | high8.8 | 4.14% (91st) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
| CVE-2021-30610US | high8.8 | 4.14% (91st) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
| CVE-2021-30624US | high8.8 | 4.13% (91st) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
| CVE-2021-30620US | high8.8 | 4.13% (91st) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
| CVE-2021-30618US | high8.8 | 4.13% (91st) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
| CVE-2021-30613US | high8.8 | 4.13% (91st) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
| CVE-2021-30607US | high8.8 | 4.13% (91st) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
| CVE-2021-30606US | high8.8 | 4.13% (91st) | — | ✗no fix | 2021-09-03 | ≤ 93.0.4577.63 |
showing 50 of 311