Microsoft Office LTSC for Mac 2024
ProduktNLcpe:2.3:a:microsoft:office_macos_2024:*:*:*:*:*:long_term_servicing_channel:*:*
Ein im Bedrohungsgraphen erfasstes Produkt; die Schwachstellen unten betreffen es bekanntermaßen.
nach Schweregrad
0critical4high0medium0low
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-2025-47166US | — | 21.6% (98th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-27751US | — | 2.48% (85th) | Exploit | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-47175US | — | 2.39% (84th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-47165US | — | 2.19% (82nd) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-47171US | — | 1.68% (77th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-47957US | — | 1.31% (71st) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-47176US | — | 0.75% (55th) | Exploit | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-29793US | — | 23.6% (98th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-47163US | — | 20.9% (98th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-29794US | — | 4.76% (92nd) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-30388US | — | 4.38% (91st) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-30382US | — | 2.61% (85th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-47172US | — | 1.75% (78th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-30378US | — | 1.42% (73rd) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-30384US | high7.0 | 1.39% (72nd) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-27744US | — | 1.20% (68th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-26687US | — | 1.14% (66th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29792US | — | 1.14% (66th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27749US | — | 1.08% (65th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27748US | — | 1.08% (65th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27745US | — | 1.08% (65th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29801US | —OT erhöht | 1.06% (65th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29800US | — | 1.06% (65th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29791US | — | 1.04% (64th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27752US | — | 1.04% (64th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27750US | — | 0.86% (58th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27746US | — | 0.86% (58th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-27747US | — | 0.82% (57th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29822US | — | 0.82% (57th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-26642US | — | 0.80% (56th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-29820US | — | 0.77% (55th) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-47162US | — | 0.76% (55th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-29823US | — | 0.69% (52nd) | — | ✗kein Fix | 2025-04-08 | ≤ vers:microsoft/unknown |
| CVE-2025-30377US | high7.8 | 0.68% (52nd) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-30386US | high7.8 | 0.68% (52nd) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-47167US | — | 0.67% (52nd) | — | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-29979US | — | 0.66% (51st) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-47169US | — | 0.65% (51st) | — | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-47164US | — | 0.65% (51st) | — | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-29977US | — | 0.65% (51st) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-47170US | — | 0.65% (51st) | — | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-29976US | — | 0.64% (51st) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-47168US | — | 0.64% (50th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-30376US | — | 0.61% (49th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-30375US | — | 0.61% (49th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-47173US | — | 0.58% (48th) | — | ✗kein Fix | 2025-06-10 | ≤ vers:microsoft/unknown |
| CVE-2025-30383US | — | 0.57% (47th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-30381US | — | 0.57% (47th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-30379US | — | 0.57% (47th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
| CVE-2025-29978US | — | 0.56% (46th) | — | ✗kein Fix | 2025-05-13 | ≤ vers:microsoft/unknown |
50 von 57 angezeigt