| CVE-2025-30397US | —OT critical | 27.3% (98th) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2023-21823US | —OT critical | 5.56% (93rd) | KEV | ✓16.0.14326.21330 | 2023-02-14 | 16.0.1 → 16.0.14326.21330 |
| CVE-2025-30400US | —OT critical | 1.92% (80th) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-32709US | —OT critical | 1.82% (79th) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-32706US | —OT critical | 2.33% (83rd) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-32701US | —OT critical | 1.42% (73rd) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29969US | — | 1.16% (67th) | Exploit | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29971US | — | 68.1% (99th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-30394US | — | 34.2% (98th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29962US | — | 15.6% (97th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-53766US | — | 8.19% (95th) | — | ✓16.0.14326.22618 | 2025-08-12 | 16.0.1 → 16.0.14326.22618 |
| CVE-2025-30388US | — | 4.38% (91st) | — | ✓16.0.14326.22502 | 2025-05-13 | 2 versions |
| CVE-2025-29968US | — | 2.02% (81st) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-26677US | — | 1.80% (78th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29960US | — | 1.53% (75th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29959US | — | 1.53% (75th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29954US | — | 1.47% (74th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29961US | — | 1.44% (73rd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29958US | — | 1.44% (73rd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29966US | — | 1.43% (73rd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29836US | — | 1.41% (72nd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29835US | — | 1.38% (72nd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29832US | — | 1.38% (72nd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29830US | — | 1.38% (72nd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29967US | — | 1.34% (71st) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-26687US | — | 1.14% (66th) | — | ✓16.0.14326.22331 | 2025-04-08 | 16.0.1 → 16.0.14326.22331 |
| CVE-2025-29956US | — | 1.12% (66th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29964US | — | 1.09% (65th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29963US | — | 1.09% (65th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29840US | — | 1.04% (64th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29831US | — | 1.01% (63rd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29974US | — | 0.74% (55th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-24063US | — | 0.72% (54th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29837US | — | 0.71% (53rd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2024-38250US | — | 0.69% (53rd) | — | ✓16.0.14326.21xxxx | 2024-09-10 | 16.0.1 → 16.0.14326.21xxxx |
| CVE-2025-29957US | — | 0.64% (50th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2023-33158US | — | 0.63% (50th) | — | ✓16.0.14326.21502 | 2023-07-11 | 16.0.1 → 16.0.14326.21502 |
| CVE-2025-29955US | medium5.5 | 0.60% (49th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29829US | — | 0.58% (47th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-32707US | — | 0.56% (46th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29970US | — | 0.53% (45th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-30385US | — | 0.53% (45th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29839US | — | 0.53% (45th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-53732US | — | 0.48% (41st) | — | ✓16.0.14326.22618 | 2025-08-12 | 16.0.1 → 16.0.14326.22618 |
| CVE-2025-21338US | — | 0.48% (41st) | — | ✓16.0.14326.22175 | 2025-01-14 | 3 versions |
| CVE-2025-29833US | — | 0.46% (39th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29842US | —OT elevated | 0.44% (38th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-29841US | — | 0.40% (34th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2025-27488US | —OT elevated | 0.40% (34th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/16.0.1|<16.0.14326.22502 |
| CVE-2023-36565US | — | 0.40% (34th) | — | ✓16.0.14326.21606 | 2023-10-10 | 16.0.1 → 16.0.14326.21606 |