Windows winget
Microsoft Office
winget:Microsoft.Office
Microsoft Office on Windows: 932 CVEs referenced, current version unknown, status indeterminable.
- Known vulnerabilities
- 932
- Still open
- 0
- KEV open
- 0
- Max CVSS (open)
- -
current version unknown
16 total (history)
9.8 historical
Known vulnerabilities (CVE)
200 undetermined
Latest matched CVE: 2026
The app's current version is unknown : impossible to determine whether each vulnerability is still present. Will be resolved at the next enrichment.
Test a different version
| CVE |
|---|
|
CVE-2026-70329
Unknown
HIGH 8.8
Network
|
|
CVE-2026-70328
Unknown
MEDIUM 6.5
Network
|
|
CVE-2026-70327
Unknown
MEDIUM 6.5
Network
|
|
CVE-2026-70318
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-70311
Unknown
HIGH 7.8
Local
|
|
CVE-2026-70310
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-68817
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68816
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68815
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68814
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68812
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68811
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68810
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68809
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-68808
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-68807
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68806
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68805
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68804
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68803
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68802
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-68801
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68800
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68799
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-68797
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-68796
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68795
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68794
Unknown
HIGH 7.8
Local
|
|
CVE-2026-68793
Unknown
HIGH 7.8
Local
|
|
CVE-2026-66810
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-66809
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-66806
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-65807
Unknown
HIGH 8.8
Network
|
|
CVE-2026-64917
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-64915
Unknown
HIGH 7.8
Local
|
|
CVE-2026-64907
Unknown
HIGH 7.8
Local
|
|
CVE-2026-64905
Unknown
HIGH 7.8
Local
|
|
CVE-2026-63531
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-63530
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-63528
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-63527
Unknown
HIGH 7.8
Local
|
|
CVE-2026-63525
Unknown
HIGH 7.8
Local
|
|
CVE-2026-63521
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-63518
Unknown
HIGH 7.8
Local
|
|
CVE-2026-62882
Unknown
MEDIUM 4.3
Network
|
|
CVE-2026-62870
Unknown
HIGH 8.8
Network
|
|
CVE-2026-55949
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55947
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55898
Unknown
MEDIUM 6.1
Local
|
|
CVE-2026-55142
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-55141
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55138
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-55137
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55136
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55134
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55132
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55131
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55130
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55128
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55127
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55124
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-55123
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55122
Unknown
HIGH 7.1
Local
|
|
CVE-2026-55120
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55058
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55055
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55054
Unknown
MEDIUM 6.5
Network
|
|
CVE-2026-55053
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55050
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-55048
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55046
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-55044
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55043
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55041
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55039
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55038
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55037
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55036
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55033
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55032
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55031
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55029
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55025
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55024
Unknown
HIGH 7.8
Local
|
|
CVE-2026-50408
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-48580
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-58618
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55948
Unknown
HIGH 7.8
Local
|
|
CVE-2026-55899
Unknown
HIGH 7.8
Local
|
|
CVE-2026-54988
Unknown
MEDIUM 6.1
Local
|
|
CVE-2026-50678
Unknown
MEDIUM 6.6
Local
|
|
CVE-2026-50675
Unknown
HIGH 7.8
Local
|
|
CVE-2026-47293
Unknown
HIGH 7.0
Local
|
|
CVE-2026-45471
Unknown
HIGH 7.8
Local
|
|
CVE-2026-45469
Unknown
HIGH 7.8
Local
|
|
CVE-2026-45458
Unknown
HIGH 8.4
Local
|
|
CVE-2026-45455
Unknown
LOW 3.3
Local
|
|
CVE-2026-44823
Unknown
HIGH 7.8
Local
|
|
CVE-2026-44822
Unknown
HIGH 8.2
Network
|
|
CVE-2026-44820
Unknown
HIGH 7.8
Local
|
|
CVE-2026-44818
Unknown
HIGH 7.0
Local
|
|
CVE-2026-44817
Unknown
HIGH 7.8
Local
|
|
CVE-2026-40421
Unknown
MEDIUM 4.3
Network
|
|
CVE-2026-40420
Unknown
HIGH 8.8
Local
|
|
CVE-2026-40418
Unknown
HIGH 7.8
Local
|
|
CVE-2026-40367
Unknown
HIGH 8.4
Local
|
|
CVE-2026-40366
Unknown
HIGH 8.4
Local
|
|
CVE-2026-40364
Unknown
HIGH 8.4
Local
|
|
CVE-2026-40363
Unknown
CRITICAL 8.4
Local
|
|
CVE-2026-40362
Unknown
HIGH 7.8
Local
|
|
CVE-2026-40361
Unknown
HIGH 8.4
Local
|
|
CVE-2026-40360
Unknown
HIGH 7.8
Local
|
|
CVE-2026-40359
Unknown
HIGH 7.8
Local
|
|
CVE-2026-40358
Unknown
HIGH 8.4
Local
|
|
CVE-2026-35440
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-35436
Unknown
HIGH 8.8
Local
|
|
CVE-2026-33115
Unknown
HIGH 8.4
Local
|
|
CVE-2026-33114
Unknown
HIGH 8.4
Local
|
|
CVE-2026-33095
Unknown
HIGH 7.8
Local
|
|
CVE-2026-32200
Unknown
HIGH 7.8
Local
|
|
CVE-2026-32199
Unknown
HIGH 7.8
Local
|
|
CVE-2026-32198
Unknown
HIGH 7.8
Local
|
|
CVE-2026-32197
Unknown
HIGH 7.8
Local
|
|
CVE-2026-32189
Unknown
HIGH 7.8
Local
|
|
CVE-2026-32188
Unknown
HIGH 7.1
Local
|
|
CVE-2026-26112
Unknown
HIGH 7.8
Local
|
|
CVE-2026-26110
Unknown
CRITICAL 8.4
Local
|
|
CVE-2026-26109
Unknown
HIGH 8.4
Local
|
|
CVE-2026-26108
Unknown
HIGH 7.8
Local
|
|
CVE-2026-26107
Unknown
HIGH 7.8
Local
|
|
CVE-2026-21511
Unknown
HIGH 7.5
Network
|
|
CVE-2026-21261
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-21260
Unknown
HIGH 7.5
Network
|
|
CVE-2026-21259
Unknown
HIGH 7.8
Local
|
|
CVE-2026-21258
Unknown
MEDIUM 5.5
Local
|
|
CVE-2026-21509
Unknown
HIGH 7.8
KEV
Local
|
|
CVE-2026-20957
Unknown
HIGH 7.8
Local
|
|
CVE-2026-20950
Unknown
HIGH 7.8
Local
|
|
CVE-2026-20948
Unknown
HIGH 7.8
Local
|
|
CVE-2026-20946
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62564
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62563
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62562
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62561
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62560
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62559
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62558
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62557
Unknown
CRITICAL 8.4
Local
|
|
CVE-2025-62556
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62555
Unknown
HIGH 7.0
Local
|
|
CVE-2025-62554
Unknown
CRITICAL 8.4
Local
|
|
CVE-2025-62553
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62203
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62202
Unknown
HIGH 7.1
Local
|
|
CVE-2025-62201
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62200
Unknown
HIGH 7.8
Local
|
|
CVE-2025-62199
Unknown
HIGH 7.8
Local
|
|
CVE-2025-60727
Unknown
HIGH 7.8
Local
|
|
CVE-2025-60726
Unknown
HIGH 7.1
Local
|
|
CVE-2025-59240
Unknown
MEDIUM 5.5
Local
|
|
CVE-2025-59238
Unknown
HIGH 7.8
Local
|
|
CVE-2025-59235
Unknown
HIGH 7.1
Local
|
|
CVE-2025-59234
Unknown
CRITICAL 7.8
Local
|
|
CVE-2025-59233
Unknown
HIGH 7.8
Local
|
|
CVE-2025-59232
Unknown
HIGH 7.1
Local
|
|
CVE-2025-59231
Unknown
HIGH 7.8
Local
|
|
CVE-2025-59227
Unknown
CRITICAL 7.8
Local
|
|
CVE-2025-59225
Unknown
HIGH 7.8
Local
|
|
CVE-2025-59224
Unknown
HIGH 7.8
Local
|
|
CVE-2025-59223
Unknown
HIGH 7.8
Local
|
|
CVE-2025-59222
Unknown
HIGH 7.8
Local
|
|
CVE-2025-59221
Unknown
HIGH 7.0
Local
|
|
CVE-2025-54908
Unknown
HIGH 7.8
Local
|
|
CVE-2025-54905
Unknown
HIGH 7.1
Local
|
|
CVE-2025-54904
Unknown
HIGH 7.8
Local
|
|
CVE-2025-54903
Unknown
HIGH 7.8
Local
|
|
CVE-2025-54902
Unknown
HIGH 7.8
Local
|
|
CVE-2025-54901
Unknown
MEDIUM 5.5
Local
|
|
CVE-2025-54900
Unknown
HIGH 7.8
Local
|
|
CVE-2025-54899
Unknown
HIGH 7.8
Local
|
|
CVE-2025-54898
Unknown
HIGH 7.8
Local
|
|
CVE-2025-54896
Unknown
HIGH 7.8
Local
|
|
CVE-2025-53761
Unknown
HIGH 7.8
Local
|
|
CVE-2025-53741
Unknown
HIGH 7.8
Local
|
|
CVE-2025-53739
Unknown
HIGH 7.8
Local
|
|
CVE-2025-53738
Unknown
HIGH 7.8
Local
|
|
CVE-2025-53737
Unknown
HIGH 7.8
Local
|
|
CVE-2025-53736
Unknown
MEDIUM 6.8
Local
|
|
CVE-2025-53735
Unknown
HIGH 7.8
Local
|
|
CVE-2025-53733
Unknown
HIGH 8.4
Local
|
|
CVE-2025-49711
Unknown
HIGH 7.8
Local
|
|
CVE-2025-49705
Unknown
HIGH 7.8
Local
|
|
CVE-2025-49703
Unknown
HIGH 7.8
Local
|
|
CVE-2025-49702
Unknown
CRITICAL 7.8
Local
|
|
CVE-2025-49700
Unknown
HIGH 7.8
Local
|
|
CVE-2025-49699
Unknown
HIGH 7.0
Local
|
|
CVE-2025-49698
Unknown
HIGH 7.8
Local
|
|
CVE-2025-49697
Unknown
CRITICAL 8.4
Local
|
|
CVE-2025-49696
Unknown
CRITICAL 8.4
Local
|
|
CVE-2025-49695
Unknown
CRITICAL 8.4
Local
|
200 indeterminable CVE(s) shown above. · Hide
0
Cumulative exposure
Low
Weighted sum capped at 100: open CVEs (max 50 pts) + KEV (max 35) + critical shared permissions (max 10) + trackers (max 8) + OS EOL (max 5). Higher score = more exposed.
-
Open CVEs +0/+50
0 open CVEs, max CVSS 0.0, EPSS 0%
-
Active KEVs +0/+35
0 CISA KEVs still open
-
Permissions +0/+10
0 critical shared permission(s)
-
Trackers +0/+8
0 identification/profiling tracker(s)
-
EOL OS +0/+5
Installed OS is end-of-life
FAQ
FAQ: Microsoft Office
Does Microsoft Office have known security vulnerabilities?
Microsoft Office (winget:Microsoft.Office) on Windows has 932 CVE referenced in NVD, 0 still open on the current version and 0 listed in the CISA KEV catalog. Absence of a CVE is not a security guarantee.
Is Microsoft Office affected by an actively exploited vulnerability (CISA KEV)?
No CVE affecting Microsoft Office (winget:Microsoft.Office) is currently in the CISA KEV catalog.