| CVE-2025-33053US | —OT critical | 87.0% (100th) | KEV | ✗no fix | 2025-06-10 | ≤ vers:unknown/1.2.0.0|<1.2.6278.0 |
| CVE-2025-33073US | —OT critical | 82.7% (100th) | KEV | ✗no fix | 2025-06-10 | ≤ vers:unknown/1.2.0.0|<1.2.6278.0 |
| CVE-2026-33824US | —OT critical | 77.1% (100th) | KEV | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-32202US | —OT critical | 70.9% (99th) | KEV | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-24054US | medium5.4OT critical | 62.3% (99th) | KEV | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2025-26633US | —OT critical | 30.4% (98th) | KEV | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2025-24985US | —OT critical | 3.89% (90th) | KEV | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2025-24993US | —OT critical | 2.22% (83rd) | KEV | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2025-24991US | —OT critical | 2.02% (81st) | KEV | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2025-24984US | —OT critical | 1.99% (81st) | KEV | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2025-24983US | —OT critical | 1.87% (79th) | KEV | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2025-47981US | — | 41.1% (99th) | Exploit | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2025-24071US | — | 23.3% (98th) | Exploit | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2021-38666US | medium6.8 | 15.2% (97th) | Exploit | ✗no fix | 2021-11-10 | ≤ N/A |
| CVE-2026-33829US | — | 3.51% (89th) | Exploit | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-24076US | — | 3.21% (88th) | Exploit | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2025-49683US | — | 2.06% (81st) | Exploit | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2025-47987US | — | 1.79% (78th) | Exploit | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2025-24035US | — | 1.72% (77th) | Exploit | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2025-49666US | — | 1.42% (73rd) | Exploit | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2025-48799US | — | 1.26% (69th) | Exploit | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2025-49677US | — | 1.12% (66th) | Exploit | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2025-32710US | — | 1.07% (65th) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/1.2.0.0|<1.2.6278.0 |
| CVE-2026-33827US | — | 0.84% (58th) | Exploit | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-49744US | — | 0.81% (57th) | Exploit | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2025-49730US | — | 0.68% (52nd) | Exploit | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2025-48804US | — | 0.65% (51st) | Exploit | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2026-33826US | — | 0.53% (45th) | Exploit | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-32223US | — | 0.52% (44th) | Exploit | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-26179US | — | 0.44% (38th) | Exploit | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2025-3052US | — | 0.43% (37th) | Exploit | ✗no fix | 2025-06-10 | ≤ vers:unknown/1.2.0.0|<1.2.6278.0 |
| CVE-2026-27912US | — | 0.41% (35th) | Exploit | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |
| CVE-2026-25250US | — | 0.12% (2nd) | Exploit | ✗no fix | 2026-08-27 | ≤ vers:unknown/* |
| CVE-2022-22017US | high9.3 | 37.1% (99th) | — | ✓1.2.3130 | 2022-05-10 | 1.2.0.0 → 1.2.3130 |
| CVE-2025-47984US | — | 23.3% (98th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2025-33071US | — | 23.2% (98th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/1.2.0.0|<1.2.6278.0 |
| CVE-2021-34535US | medium6.8 | 21.9% (98th) | — | ✓publication | 2021-08-12 | 1.2.0.0 → publication |
| CVE-2022-21990US | medium6.8 | 18.8% (97th) | — | ✓1.2.2925.0 | 2022-03-09 | 1.2.0.0 → 1.2.2925.0 |
| CVE-2025-33070US | — | 9.86% (96th) | — | ✗no fix | 2025-06-10 | ≤ vers:unknown/1.2.0.0|<1.2.6278.0 |
| CVE-2025-49724US | — | 9.81% (96th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/1.2.0.0|<1.2.6353.0 |
| CVE-2021-38665US | medium4.3 | 7.02% (94th) | — | ✓1.2.2600 | 2021-11-10 | 1.2.0.0 → 1.2.2600 |
| CVE-2021-1669US | medium6.5 | 3.20% (88th) | — | ✓publication | 2021-01-12 | 1.2.0.0 → publication |
| CVE-2025-26645US | — | 3.18% (88th) | — | ✓1.2.6017.0 | 2025-03-11 | 4 versions |
| CVE-2025-21247US | — | 3.05% (87th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/1.2.0.0|<1.2.6017.0 |
| CVE-2022-21851US | high9.3 | 2.78% (86th) | — | ✓1.2.2691.0 | 2022-01-11 | 1.2.0.0 → 1.2.2691.0 |
| CVE-2022-21850US | high9.3 | 2.78% (86th) | — | ✓1.2.2691.0 | 2022-01-11 | 1.2.0.0 → 1.2.2691.0 |
| CVE-2022-26940US | medium4.0 | 2.68% (86th) | — | ✓1.2.3130 | 2022-05-10 | 1.2.0.0 → 1.2.3130 |
| CVE-2022-22015US | medium4.0 | 2.68% (86th) | — | ✓1.2.3130 | 2022-05-10 | 1.2.0.0 → 1.2.3130 |
| CVE-2022-24503US | medium5.0 | 2.44% (84th) | — | ✓1.2.2925.0 | 2022-03-09 | 1.2.0.0 → 1.2.2925.0 |
| CVE-2026-27914US | — | 2.43% (84th) | — | ✗no fix | 2026-04-14 | ≤ vers:unknown/* |