| CVE-2025-49704US | —OT critical | 100.0% (100th) | KEV | ✗no fix | 2025-07-08 | ≤ vers:unknown/2.0.0|<7.10.1(100772025102901) |
| CVE-2025-49706US | —OT critical | 99.1% (100th) | KEV | ✗no fix | 2025-07-08 | ≤ vers:unknown/2.0.0|<7.10.1(100772025102901) |
| CVE-2026-65660US | high8.8OT critical | 8.19% (95th) | KEV | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-63520US | — | 0.96% (61st) | Exploit | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2025-53783US | — | 0.81% (57th) | Exploit | ✓7.10.1 (100772025102901) | 2025-08-12 | 2.0.0 → 7.10.1 (100772025102901) |
| CVE-2024-38197US | — | 16.8% (97th) | — | ✓7.13.0 | 2024-08-13 | 2.0.0 → 7.13.0 |
| CVE-2025-47994US | high8.6 | 3.28% (88th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/2.0.0|<7.10.1(100772025102901) |
| CVE-2021-24114US | low3.5 | 3.16% (88th) | — | ✓publication | 2021-02-25 | 2.0.0 → publication |
| CVE-2022-21965US | medium5.0 | 2.96% (87th) | — | ✓2.5.0 | 2022-02-09 | 2.0.0 → 2.5.0 |
| CVE-2023-29328US | — | 2.15% (82nd) | — | ✓5.12.1 | 2023-08-08 | 2.0.0 → 5.12.1 |
| CVE-2026-66808US | — | 2.04% (81st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-66805US | — | 2.04% (81st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-65663US | — | 2.04% (81st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-65658US | — | 2.04% (81st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-64901US | — | 2.04% (81st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-63514US | — | 2.04% (81st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2023-29330US | — | 2.00% (81st) | — | ✓5.12.1 | 2023-08-08 | 2.0.0 → 5.12.1 |
| CVE-2026-63516US | — | 1.87% (79th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-70321US | — | 1.69% (77th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-65665US | — | 1.69% (77th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-50515US | — | 1.69% (77th) | — | ✗no fix | 2026-08-07 | ≤ vers:unknown/* |
| CVE-2025-49701US | — | 1.29% (70th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/2.0.0|<7.10.1(100772025102901) |
| CVE-2026-62837US | — | 1.23% (69th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-70306US | — | 1.01% (63rd) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-70324US | — | 0.94% (61st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-64921US | —OT elevated | 0.94% (61st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-62827US | — | 0.94% (61st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-65768US | critical9.8 | 0.94% (61st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-65769US | high7.5 | 0.92% (60th) | — | ✓8.14.1 | 2026-08-11 | 4 versions |
| CVE-2026-70328US | — | 0.92% (60th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-70327US | — | 0.92% (60th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-62839US | — | 0.91% (60th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-58639US | — | 0.91% (60th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-70332US | — | 0.86% (58th) | — | ✗no fix | 2026-08-07 | ≤ vers:unknown/* |
| CVE-2026-70329US | — | 0.82% (57th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-65807US | — | 0.82% (57th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-65667US | —OT elevated | 0.80% (56th) | — | ✗no fix | 2026-08-07 | ≤ vers:unknown/* |
| CVE-2026-70355US | high8.7 | 0.78% (56th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-70326US | — | 0.78% (56th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2025-49703US | — | 0.77% (55th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/2.0.0|<7.10.1(100772025102901) |
| CVE-2026-63512US | —OT elevated | 0.73% (54th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2026-62896US | — | 0.69% (53rd) | — | ✗no fix | 2026-08-07 | ≤ vers:unknown/* |
| CVE-2025-49695US | — | 0.69% (53rd) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/2.0.0|<7.10.1(100772025102901) |
| CVE-2026-62882US | — | 0.67% (52nd) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2025-49702US | — | 0.66% (51st) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/2.0.0|<7.10.1(100772025102901) |
| CVE-2026-64900US | medium5.4 | 0.65% (51st) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |
| CVE-2025-49698US | — | 0.65% (51st) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/2.0.0|<7.10.1(100772025102901) |
| CVE-2026-62836US | critical10.0 | 0.65% (51st) | — | ✗no fix | 2026-08-07 | ≤ vers:unknown/* |
| CVE-2025-49696US | — | 0.64% (50th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/2.0.0|<7.10.1(100772025102901) |
| CVE-2026-57105US | medium5.4 | 0.62% (49th) | — | ✗no fix | 2026-08-11 | ≤ vers:unknown/* |