| CVE-2025-49704US | —OT critical | 100.0% (100th) | KEV | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0|<16.0.5508.1000 |
| CVE-2025-49706US | —OT critical | 99.1% (100th) | KEV | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0|<16.0.5508.1000 |
| CVE-2026-32201US | medium6.5OT critical | 43.4% (99th) | KEV | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| 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.0|<16.0.5504.1000 |
| CVE-2025-47175US | — | 2.39% (84th) | Exploit | ✓16.0.5504.1000 | 2025-06-10 | 2 versions |
| CVE-2025-47165US | — | 2.19% (82nd) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-47171US | — | 1.68% (77th) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-47957US | — | 1.31% (71st) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-47176US | — | 0.75% (55th) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-47163US | — | 20.9% (98th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2026-20945US | medium5.4 | 19.1% (97th) | — | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2021-27056US | medium6.8 | 4.30% (91st) | — | ✓publication | 2021-03-11 | 16.0.0 → publication |
| CVE-2020-17124US | high9.3 | 3.46% (89th) | — | ✓publication | 2020-12-10 | 16.0.0 → publication |
| CVE-2025-47994US | high8.6 | 3.28% (88th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0|<16.0.5508.1000 |
| CVE-2025-59237US | — | 2.46% (84th) | — | ✗no fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-47172US | — | 1.75% (78th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-59228US | — | 1.36% (72nd) | — | ✗no fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-49701US | — | 1.29% (70th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0|<16.0.5508.1000 |
| CVE-2024-20673US | — | 1.18% (67th) | — | ✓16.0.5435.1000 | 2024-02-13 | 16.0.0 → 16.0.5435.1000 |
| CVE-2025-55243US | — | 1.16% (67th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2024-38171US | — | 0.93% (60th) | — | ✓16.0.5461.1000 | 2024-08-13 | 16.0.0 → 16.0.5461.1000 |
| CVE-2025-53799US | — | 0.84% (58th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-54906US | — | 0.79% (56th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-49703US | — | 0.77% (55th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0|<16.0.5508.1000 |
| CVE-2025-47162US | — | 0.76% (55th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-49695US | — | 0.69% (53rd) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0|<16.0.5508.1000 |
| CVE-2025-47167US | — | 0.67% (52nd) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-49702US | — | 0.66% (51st) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0|<16.0.5508.1000 |
| CVE-2025-59235US | — | 0.65% (51st) | — | ✗no fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-47169US | — | 0.65% (51st) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-47164US | — | 0.65% (51st) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-49698US | — | 0.65% (51st) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0|<16.0.5508.1000 |
| CVE-2025-47170US | — | 0.65% (51st) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-54901US | — | 0.64% (50th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-49696US | — | 0.64% (50th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0|<16.0.5508.1000 |
| CVE-2025-47168US | — | 0.64% (50th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-54905US | — | 0.62% (50th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-48812US | — | 0.61% (49th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/16.0.0|<16.0.5508.1000 |
| CVE-2025-54910US | — | 0.61% (49th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-59234US | — | 0.60% (48th) | — | ✗no fix | 2025-10-14 | ≤ vers:unknown/* |
| CVE-2025-54908US | — | 0.59% (48th) | — | ✓16.0.5517.1000 | 2025-09-09 | 2 versions |
| CVE-2025-47173US | — | 0.58% (48th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/16.0.0|<16.0.5504.1000 |
| CVE-2025-54904US | — | 0.57% (47th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-54903US | — | 0.57% (47th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-54902US | — | 0.57% (47th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-54900US | — | 0.57% (47th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-54899US | — | 0.57% (47th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-54898US | — | 0.57% (47th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |
| CVE-2025-54896US | — | 0.57% (47th) | — | ✗no fix | 2025-09-09 | ≤ vers:unknown/* |