microsoft exchange server subscription edition
ProduktUScpe:2.3:a:microsoft:exchange_server_subscription_edition:*:*:*:*:*:*:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
2critical13high9medium0low
aktualisiert 2026-10-28
| ID | Schweregrad CVSS-Basis-Schweregrad und -Wert (0–10). | EPSS FIRST.org-Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen, mit Perzentil-Rang unter allen CVEs. | ausnutzbar Auf CISAs Liste bekannter ausgenutzter Schwachstellen (KEV) oder ein öffentlicher Exploit liegt vor. | behoben Ob für einen betroffenen Bereich eine behobene Version vorliegt. | veröffentlicht | betroffen |
|---|
| CVE-2026-42897US | medium6.1OT kritisch | 70.7% (99th) | KEV | ✓15.02.2562.043 | 2026-05-14 | < 15.02.2562.043 |
| CVE-2025-53786US | — | 7.59% (95th) | Exploit | ✓15.02.2562.017 | 2025-08-06 | < 15.02.2562.017 |
| CVE-2026-96940US | high8.8 | 2.75% (86th) | Exploit | ✓15.02.2562.053 | 2026-10-02 | < 15.02.2562.053 |
| CVE-2026-45504US | — | 1.18% (68th) | Exploit | ✓15.02.2562.043 | 2026-06-09 | < 15.02.2562.043 |
| CVE-2026-62911US | —OT erhöht | 0.69% (53rd) | Exploit | ✓15.02.2562.046 | 2026-08-11 | < 15.02.2562.046 |
| CVE-2026-45502US | — | 20.3% (97th) | — | ✓15.02.2562.043 | 2026-06-09 | < 15.02.2562.043 |
| CVE-2026-21527US | —OT erhöht | 8.26% (95th) | — | ✓15.02.2562.037 | 2026-02-10 | < 15.02.2562.037 |
| CVE-2026-55009US | — | 2.51% (85th) | — | ✓15.02.2562.045 | 2026-07-14 | < 15.02.2562.045 |
| CVE-2026-62912US | — | 1.98% (80th) | — | ✓15.02.2562.046 | 2026-08-11 | < 15.02.2562.046 |
| CVE-2025-25005US | medium6.5 | 1.41% (72nd) | — | ✓15.02.2562.020 | 2025-08-12 | < 15.02.2562.020 |
| CVE-2025-33051US | — | 1.27% (70th) | — | ✓15.02.2562.020 | 2025-08-12 | < 15.02.2562.020 |
| CVE-2026-69378US | high7.5 | 1.17% (67th) | — | ✓15.02.2562.049 | 2026-09-08 | < 15.02.2562.049 |
| CVE-2025-64666US | high7.5 | 1.02% (63rd) | — | ✓15.02.2562.035 | 2025-12-09 | < 15.02.2562.035 |
| CVE-2025-59248US | high7.5 | 1.02% (63rd) | — | ✓15.02.2562.029 | 2025-10-14 | < 15.02.2562.029 |
| CVE-2026-55005US | — | 1.01% (63rd) | — | ✓15.02.2562.045 | 2026-07-14 | < 15.02.2562.045 |
| CVE-2026-62910US | high8.8 | 1.00% (63rd) | — | ✓15.02.2562.046 | 2026-08-11 | < 15.02.2562.046 |
| CVE-2026-65813US | high8.8 | 0.94% (61st) | — | ✓15.02.2562.046 | 2026-08-11 | < 15.02.2562.046 |
| CVE-2026-69355US | high8.8 | 0.91% (60th) | — | ✓15.02.2562.049 | 2026-09-08 | < 15.02.2562.049 |
| CVE-2026-62913US | — | 0.91% (60th) | — | ✓15.02.2562.046 | 2026-08-11 | < 15.02.2562.046 |
| CVE-2025-25006US | — | 0.89% (59th) | — | ✓15.02.2562.020 | 2025-08-12 | < 15.02.2562.020 |
| CVE-2025-25007US | — | 0.87% (59th) | — | ✓15.02.2562.020 | 2025-08-12 | < 15.02.2562.020 |
| CVE-2026-55008US | — | 0.86% (58th) | — | ✓15.02.2562.045 | 2026-07-14 | < 15.02.2562.045 |
| CVE-2026-69641US | critical9.1OT erhöht | 0.86% (58th) | — | ✓15.02.2562.049 | 2026-09-08 | < 15.02.2562.049 |
| CVE-2026-69361US | medium6.5 | 0.84% (58th) | — | ✓15.02.2562.049 | 2026-09-08 | < 15.02.2562.049 |
| CVE-2025-59249US | — | 0.83% (57th) | — | ✓15.02.2562.029 | 2025-10-14 | < 15.02.2562.029 |
| CVE-2025-64667US | — | 0.80% (56th) | — | ✓15.02.2562.035 | 2025-12-09 | < 15.02.2562.035 |
| CVE-2026-69356US | critical9.3 | 0.76% (55th) | — | ✓15.02.2562.049 | 2026-09-08 | < 15.02.2562.049 |
| CVE-2026-55007US | high8.1 | 0.71% (53rd) | — | ✓15.02.2562.049 | 2026-09-08 | < 15.02.2562.049 |
| CVE-2026-69380US | high8.1OT erhöht | 0.69% (53rd) | — | ✓15.02.2562.049 | 2026-09-08 | < 15.02.2562.049 |
| CVE-2026-69375US | medium6.5 | 0.64% (51st) | — | ✓15.02.2562.049 | 2026-09-08 | < 15.02.2562.049 |
| CVE-2026-62915US | —OT erhöht | 0.64% (51st) | — | ✓15.02.2562.046 | 2026-08-11 | < 15.02.2562.046 |
| CVE-2026-45583US | high8.1 | 0.52% (44th) | — | ✓15.02.2562.043 | 2026-06-09 | < 15.02.2562.043 |
| CVE-2026-69382US | medium5.9OT erhöht | 0.47% (41st) | — | ✓15.02.2562.049 | 2026-09-08 | < 15.02.2562.049 |
| CVE-2026-62914US | medium5.4 | 0.45% (39th) | — | ✓15.02.2562.046 | 2026-08-11 | < 15.02.2562.046 |
| CVE-2026-45503US | medium6.5 | 0.45% (39th) | — | ✓15.02.2562.043 | 2026-06-09 | < 15.02.2562.043 |
| CVE-2026-87696US | high7.5 | 0.42% (36th) | — | ✓15.02.2562.056 | 2026-10-13 | < 15.02.2562.056 |
| CVE-2026-45501US | medium6.1 | 0.40% (34th) | — | ✓15.02.2562.043 | 2026-06-09 | < 15.02.2562.043 |
| CVE-2026-45500US | — | 0.38% (31st) | — | ✓15.02.2562.043 | 2026-06-09 | < 15.02.2562.043 |
| CVE-2025-53782US | high7.8 | 0.36% (29th) | — | ✓15.02.2562.029 | 2025-10-14 | < 15.02.2562.029 |
| CVE-2026-47631US | medium5.4 | 0.35% (29th) | — | ✓15.02.2562.043 | 2026-06-09 | < 15.02.2562.043 |
| CVE-2026-55006US | — | 0.30% (22nd) | — | ✓15.02.2562.045 | 2026-07-14 | < 15.02.2562.045 |
| CVE-2026-87695US | high7.8 | 0.29% (22nd) | — | ✓15.02.2562.056 | 2026-10-13 | < 15.02.2562.056 |