CVE-2026-58289 |
critical
|
9.0 |
0.0199
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-83831 |
high
|
8.8 |
0.0077
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.48
|
|
CVE-2026-85898 |
high
|
8.8 |
0.0077
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.48
|
|
CVE-2026-72984 |
high
|
8.8 |
0.0082
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 152.0.4191.53
|
|
CVE-2026-56645 |
high
|
8.8 |
0.0082
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-57974 |
high
|
8.8 |
0.0082
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-57981 |
high
|
8.8 |
0.0082
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-88077 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.62
|
|
CVE-2026-96192 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 155.0.4283.45
|
|
CVE-2026-96196 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 156.0.4314.50
|
|
CVE-2026-96203 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 155.0.4283.45
|
|
CVE-2026-96202 |
high
|
8.8 |
0.0093
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-96951 |
high
|
8.8 |
0.0981
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.62
|
KEV
|
CVE-2026-85890 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-85897 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-96198 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-96199 |
high
|
8.8 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 154.0.4258.37
|
|
CVE-2026-57983 |
high
|
8.7 |
0.0065
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-70341 |
high
|
8.5 |
0.0064
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 152.0.4191.52
|
|
CVE-2026-58281 |
high
|
8.3 |
0.0096
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58284 |
high
|
8.3 |
0.0056
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58285 |
high
|
8.3 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58287 |
high
|
8.3 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58288 |
high
|
8.3 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58295 |
high
|
8.3 |
0.0051
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58596 |
high
|
8.3 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-72970 |
high
|
8.3 |
0.0073
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 151.0.4129.86
|
|
CVE-2026-58525 |
high
|
8.2 |
0.0051
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.50
|
|
CVE-2026-58282 |
high
|
8.1 |
0.0042
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58283 |
high
|
8.1 |
0.0044
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58286 |
high
|
8.1 |
0.0042
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58293 |
high
|
8.1 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-66318 |
high
|
8.1 |
0.0036
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 151.0.4129.59
|
|
CVE-2026-85899 |
high
|
8.1 |
—
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 155.0.4283.45
|
|
CVE-2026-57985 |
high
|
7.6 |
0.0072
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-57975 |
high
|
7.5 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-57984 |
high
|
7.5 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-57986 |
high
|
7.5 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-57992 |
high
|
7.5 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58276 |
high
|
7.5 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58290 |
high
|
7.5 |
0.0043
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58292 |
high
|
7.5 |
0.0048
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58294 |
high
|
7.5 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-58299 |
high
|
7.5 |
0.0047
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-66315 |
high
|
7.5 |
0.0061
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 151.0.4129.59
|
|
CVE-2026-62765 |
high
|
7.5 |
0.0044
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 149.0.4022.62
|
|
CVE-2026-57989 |
high
|
7.4 |
0.0043
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.99
|
|
CVE-2026-57990 |
high
|
7.4 |
0.0092
|
Microsoft |
Microsoft Edge (Chromium-based) |
-
|
|
CVE-2026-57991 |
high
|
7.4 |
0.0104
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|
CVE-2026-57993 |
high
|
7.4 |
0.0088
|
Microsoft |
Microsoft Edge (Chromium-based) |
1.0.0.0
< 150.0.4078.48
|
|