| ID | severity CVSS base severity and score (0–10). | EPSS FIRST.org probability this is exploited in the next 30 days, with its percentile rank among all CVEs. | exploitable On CISA's Known Exploited Vulnerabilities list, or a public exploit is on file. | patched Whether a fixed version is on file for an affecting range. | published | affected |
|---|
| CVE-2024-38475US | critical9.1OT critical | 100.0% (100th) | KEV | ✓19.10.0.5 | 2024-07-01 | < 19.10.0.5 |
| CVE-2025-32433US | —OT critical | 98.9% (100th) | KEV | ✓19.13 | 2025-04-16 | 3 versions |
| CVE-2023-29336US | —OT critical | 41.2% (99th) | KEV | ✗no fix | 2023-05-09 | ≤ BMR <19.9.0.6 |
| CVE-2025-6558US | —OT critical | 10.9% (96th) | KEV | ✗no fix | 2025-07-15 | 2 versions |
| CVE-2025-41244US | —OT critical | 8.63% (95th) | KEV | ✗no fix | 2025-09-29 | 5 versions |
| CVE-2025-39682US | critical9.8OT critical | 3.25% (88th) | KEV | ✗no fix | 2025-09-05 | ≤ vProxy <19.14 |
| CVE-2024-36971US | high7.8OT critical | 2.70% (86th) | KEV | ✗no fix | 2024-06-10 | ≤ vProxy <19.12 |
| CVE-2025-39964US | medium5.5OT critical | 1.57% (75th) | KEV | ✗no fix | 2025-10-13 | ≤ vProxy <19.14 |
| CVE-2025-38352US | —OT critical | 1.36% (71st) | KEV | ✗no fix | 2025-07-22 | ≤ vProxy <19.14 |
| CVE-2016-2183US | high7.5OT high | 94.7% (100th) | Exploit | ✓19.10 | 2016-09-01 | < 19.10 |
| CVE-2023-45288US | — | 92.0% (100th) | Exploit | ✓19.10.0.5 | 2024-04-04 | < 19.10.0.5 |
| CVE-2024-27316US | high7.5 | 91.3% (100th) | Exploit | ✓19.10.0.5 | 2024-04-04 | < 19.10.0.5 |
| CVE-2024-30255US | high7.5 | 87.8% (100th) | Exploit | ✓19.10.0.5 | 2024-04-04 | < 19.10.0.5 |
| CVE-2021-28164US | medium5.3OT high | 82.4% (100th) | Exploit | ✓virtual 19.9.0.2 | 2021-04-01 | 2 versions |
| CVE-2024-47076US | high8.6 | 79.9% (100th) | Exploit | ✗no fix | 2024-09-26 | ≤ vProxy <19.14 |
| CVE-2023-38408US | critical9.8 | 79.7% (100th) | Exploit | ✗no fix | 2023-07-20 | ≤ vProxy OVA <19.9.0.5 |
| CVE-2024-38472US | — | 69.5% (99th) | Exploit | ✓19.10.0.5 | 2024-07-01 | < 19.10.0.5 |
| CVE-2025-55752US | — | 64.4% (99th) | Exploit | ✓19.13.0.3 | 2025-10-27 | < 19.13.0.3 |
| CVE-2024-47175US | critical9.8 | 63.6% (99th) | Exploit | ✗no fix | 2024-09-26 | ≤ vProxy <19.14 |
| CVE-2023-38039US | high7.5 | 56.4% (99th) | Exploit | ✗no fix | 2023-09-15 | 2 versions |
| CVE-2024-47176US | — | 50.6% (99th) | Exploit | ✗no fix | 2024-09-26 | ≤ vProxy <19.14 |
| CVE-2015-6834US | critical9.8 | 46.8% (99th) | Exploit | ✓19.13 | 2016-05-16 | 2 versions |
| CVE-2024-38476US | critical9.8 | 41.6% (99th) | Exploit | ✓19.10.0.5 | 2024-07-01 | < 19.10.0.5 |
| CVE-2015-6835US | critical9.8 | 36.2% (98th) | Exploit | ✓19.13 | 2016-05-16 | 2 versions |
| CVE-2024-50379US | — | 31.8% (98th) | Exploit | ✓19.13.0.1 | 2024-12-17 | < 19.13.0.1 |
| CVE-2025-48988US | — | 30.4% (98th) | Exploit | ✗no fix | 2025-06-16 | 2 versions |
| CVE-2024-38473US | — | 25.9% (98th) | Exploit | ✓19.10.0.5 | 2024-07-01 | < 19.10.0.5 |
| CVE-2024-24549US | — | 23.1% (98th) | Exploit | ✓19.10.0.5 | 2024-03-13 | < 19.10.0.5 |
| CVE-2018-18065US | medium6.5 | 17.5% (97th) | Exploit | ✓19.11.0.6 | 2018-10-08 | 2 versions |
| CVE-2020-15778US | high7.4 | 13.7% (96th) | Exploit | ✗no fix | 2020-07-24 | 2 versions |
| CVE-2019-19012US | critical9.8 | 10.6% (96th) | Exploit | ✗no fix | 2019-11-17 | 2 versions |
| CVE-2025-39946US | medium5.5 | 10.3% (96th) | Exploit | ✗no fix | 2025-10-04 | ≤ vProxy <19.14 |
| CVE-2016-1839US | medium5.5 | 7.35% (94th) | Exploit | ✓19.11.0.2 | 2016-05-20 | 5 versions |
| CVE-2016-3627US | high7.5 | 7.03% (94th) | Exploit | ✓19.11.0.5 | 2016-05-17 | 5 versions |
| CVE-2016-1838US | medium5.5 | 6.94% (94th) | Exploit | ✓19.13 | 2016-05-20 | 5 versions |
| CVE-2019-19204US | high7.5 | 6.89% (94th) | Exploit | ✗no fix | 2019-11-21 | 2 versions |
| CVE-2024-52316US | — | 6.25% (94th) | Exploit | ✓19.13.0.1 | 2024-11-18 | < 19.13.0.1 |
| CVE-2017-5124US | medium6.1 | 5.15% (92nd) | Exploit | ✓19.13 | 2018-02-07 | 2 versions |
| CVE-2022-48565US | critical9.8 | 5.07% (92nd) | Exploit | ✓19.11 | 2023-08-22 | 3 versions |
| CVE-2025-53020US | — | 4.96% (92nd) | Exploit | ✗no fix | 2025-07-10 | 2 versions |
| CVE-2015-8710US | critical9.8 | 4.92% (92nd) | Exploit | ✓19.11.0.2 | 2016-04-11 | 5 versions |
| CVE-2024-40725US | medium5.3 | 4.42% (91st) | Exploit | ✓19.10.0.5 | 2024-07-18 | < 19.10.0.5 |
| CVE-2019-19203US | high7.5 | 4.05% (91st) | Exploit | ✗no fix | 2019-11-21 | 2 versions |
| CVE-2023-38709US | — | 3.91% (90th) | Exploit | ✓19.10.0.5 | 2024-04-04 | < 19.10.0.5 |
| CVE-2025-8671US | — | 3.62% (89th) | Exploit | ✗no fix | 2025-08-13 | 2 versions |
| CVE-2006-20001US | high7.5 | 3.55% (89th) | Exploit | ✓19.7.1.1 | 2023-01-17 | 3 versions |
| CVE-2024-23653US | critical9.8OT high | 3.45% (89th) | Exploit | ✓19.10.0.2 | 2024-01-31 | < 19.10.0.2 |
| CVE-2025-49125US | —OT elevated | 3.44% (89th) | Exploit | ✗no fix | 2025-06-16 | 2 versions |
| CVE-2025-46701US | — | 3.14% (88th) | Exploit | ✓19.13.0.1 | 2025-05-29 | < 19.13.0.1 |
| CVE-2023-29324US | medium6.5 | 2.87% (87th) | Exploit | ✗no fix | 2023-05-09 | ≤ BMR <19.9.0.6 |
showing 50 of 4,574