Microsoft Microsoft Office for Android

Name: Microsoft Microsoft Office for Android
Brand: Microsoft

productEU

A product tracked in the threat graph; the vulnerabilities below are known to affect it.

by severity

5critical79high79medium6low

updated 2026-10-27

vulnerabilities (459)

Related CVEs.

sort

ID	severity	EPSS	exploitable	patched	published	affected
CVE-2025-49704US	—OT critical	100.0% (100th)	KEV	no fix	2025-07-08	≤ vers:unknown/16.0.1\|<16.0.19029.20000
CVE-2025-49706US	—OT critical	99.1% (100th)	KEV	no fix	2025-07-08	≤ vers:unknown/16.0.1\|<16.0.19029.20000
CVE-2026-55040US	—OT critical	69.5% (99th)	KEV	no fix	2026-07-14	≤ vers:unknown/*
CVE-2025-30397US	—OT critical	27.3% (98th)	KEV	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2023-21823US	—OT critical	5.56% (93rd)	KEV	16.0.16130.20156	2023-02-14	16.0.1 → 16.0.16130.20156
CVE-2026-50522US	—OT critical	3.04% (87th)	KEV	no fix	2026-07-14	≤ vers:unknown/*
CVE-2025-30400US	—OT critical	1.92% (80th)	KEV	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2025-32709US	—OT critical	1.82% (79th)	KEV	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2026-56164US	critical9.8OT critical	1.01% (63rd)	KEV	no fix	2026-07-14	≤ vers:unknown/*
CVE-2026-58644US	—OT critical	15.9% (97th)	KEV	no fix	2026-07-14	≤ vers:unknown/*
CVE-2025-32706US	—OT critical	2.33% (83rd)	KEV	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2025-32701US	—OT critical	1.42% (73rd)	KEV	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2025-54897US	—	21.7% (98th)	Exploit	no fix	2025-09-09	≤ vers:unknown/*
CVE-2025-47166US	—	21.6% (98th)	Exploit	no fix	2025-06-10	≤ vers:unknown/16.0.1\|<16.0.18925.20000
CVE-2026-26114US	—	3.08% (88th)	Exploit	no fix	2026-03-10	≤ vers:unknown/*
CVE-2025-47175US	—	2.39% (84th)	Exploit	no fix	2025-06-10	≤ vers:unknown/16.0.1\|<16.0.18925.20000
CVE-2025-47165US	—	2.19% (82nd)	Exploit	no fix	2025-06-10	≤ vers:unknown/16.0.1\|<16.0.18925.20000
CVE-2025-47171US	—	1.68% (77th)	Exploit	no fix	2025-06-10	≤ vers:unknown/16.0.1\|<16.0.18925.20000
CVE-2025-47957US	—	1.31% (71st)	Exploit	no fix	2025-06-10	≤ vers:unknown/16.0.1\|<16.0.18925.20000
CVE-2025-29969US	—	1.16% (67th)	Exploit	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2025-47176US	—	0.75% (55th)	Exploit	no fix	2025-06-10	≤ vers:unknown/16.0.1\|<16.0.18925.20000
CVE-2025-29971US	—	68.1% (99th)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2026-45484US	—	35.2% (98th)	—	no fix	2026-06-09	≤ vers:unknown/*
CVE-2025-30394US	—	34.2% (98th)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2026-33112US	—	31.1% (98th)	—	no fix	2026-05-12	≤ vers:unknown/*
CVE-2025-47163US	—	20.9% (98th)	—	no fix	2025-06-10	≤ vers:unknown/16.0.1\|<16.0.18925.20000
CVE-2025-29962US	—	15.6% (97th)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2025-53766US	—	8.19% (95th)	—	16.0.19127.20000	2025-08-12	16.0.1 → 16.0.19127.20000
CVE-2025-60724US	—	6.29% (94th)	—	16.0.19426.20044	2025-11-11	2 versions
CVE-2026-40364US	—	4.42% (91st)	—	no fix	2026-05-12	≤ vers:unknown/*
CVE-2025-30388US	—	4.38% (91st)	—	16.0.18827.20000	2025-05-13	2 versions
CVE-2025-47994US	high8.6	3.28% (88th)	—	no fix	2025-07-08	≤ vers:unknown/16.0.1\|<16.0.19029.20000
CVE-2025-59237US	—	2.46% (84th)	—	no fix	2025-10-14	≤ vers:unknown/*
CVE-2025-62204US	—	2.21% (82nd)	—	no fix	2025-11-11	≤ vers:unknown/*
CVE-2026-35439US	—	2.03% (81st)	—	no fix	2026-05-12	≤ vers:unknown/*
CVE-2025-29968US	—	2.02% (81st)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2026-33110US	—	1.97% (80th)	—	no fix	2026-05-12	≤ vers:unknown/*
CVE-2026-40368US	—	1.82% (79th)	—	no fix	2026-05-12	≤ vers:unknown/*
CVE-2025-26677US	—	1.80% (78th)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2025-47172US	—	1.75% (78th)	—	no fix	2025-06-10	≤ vers:unknown/16.0.1\|<16.0.18925.20000
CVE-2026-40357US	—	1.70% (77th)	—	no fix	2026-05-12	≤ vers:unknown/*
CVE-2026-45454US	high8.8	1.63% (76th)	—	no fix	2026-06-09	≤ vers:unknown/*
CVE-2025-29960US	—	1.53% (75th)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2025-29959US	—	1.53% (75th)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2025-29954US	—	1.47% (74th)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2025-29961US	—	1.44% (73rd)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2025-29958US	—	1.44% (73rd)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2026-20846US	—	1.43% (73rd)	—	16.0.19822.20000	2026-02-10	16.0.1 → 16.0.19822.20000
CVE-2025-29966US	—	1.43% (73rd)	—	no fix	2025-05-13	≤ vers:unknown/16.0.1\|<16.0.18827.20000
CVE-2026-26106US	—	1.42% (73rd)	—	no fix	2026-03-10	≤ vers:unknown/*

showing 50 of 459

weaknesses (8)

The flaw types (CWEs) most of these CVEs share.

CWE-122Heap-based Buffer Overflow89 CVEs
CWE-416Use After Free83 CVEs
CWE-125Out-of-bounds Read75 CVEs
CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')35 CVEs
CWE-121Stack-based Buffer Overflow18 CVEs
CWE-502Deserialization of Untrusted Data17 CVEs
CWE-822Untrusted Pointer Dereference17 CVEs
CWE-787Out-of-bounds Write16 CVEs

sources (3)

Which sources assert this record, and when.

NLNCSC-NL (CSAF)442 CVEs
EUEU Vulnerability Database (ENISA)40 CVEs
USMicrosoft MSRC (CSAF)20 CVEs

scry

Products carry known vulnerabilities once they are exposed to the internet. See what is exposed on your perimeter with a free passive scan.

Free scan