| CVE-2025-31324US | critical9.8OT critical | 99.5% (100th) | KEV | ✗no fix | 2025-04-24 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42999US | —OT critical | 12.9% (96th) | KEV | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2024-53677US | critical9.8 | 72.4% (99th) | Exploit | ✗no fix | 2024-12-11 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42957US | — | 1.65% (76th) | Exploit | ✗no fix | 2025-08-12 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42967US | — | 1.02% (63rd) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42946US | — | 0.95% (61st) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-27429US | — | 0.79% (56th) | — | ✗no fix | 2025-04-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42980US | — | 0.77% (55th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42963US | — | 0.75% (55th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42966US | — | 0.73% (54th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42964US | — | 0.73% (54th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42950US | — | 0.70% (53rd) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42959US | — | 0.56% (46th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42953US | —OT elevated | 0.49% (42nd) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42951US | —OT elevated | 0.49% (42nd) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-43010US | — | 0.47% (41st) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42955US | —OT elevated | 0.46% (40th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42954US | — | 0.45% (39th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42952US | —OT elevated | 0.43% (37th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-30018US | high7.5 | 0.42% (36th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42976US | — | 0.42% (36th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2024-39592US | medium6.5OT elevated | 0.42% (36th) | — | ✗no fix | 2024-07-09 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-43008US | —OT elevated | 0.36% (30th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-31331US | —OT elevated | 0.36% (30th) | — | ✗no fix | 2025-04-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-31329US | — | 0.36% (30th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-43004US | —OT elevated | 0.36% (29th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-43011US | —OT elevated | 0.36% (29th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42961US | —OT elevated | 0.35% (29th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-43003US | — | 0.33% (26th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42949US | —OT elevated | 0.32% (25th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42943US | — | 0.32% (25th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-23194US | —OT elevated | 0.32% (25th) | — | ✗no fix | 2025-03-11 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-43002US | — | 0.31% (24th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-43006US | — | 0.29% (22nd) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42970US | — | 0.28% (21st) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42997US | — | 0.28% (20th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-31326US | — | 0.28% (20th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42968US | medium4.3OT elevated | 0.27% (19th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42974US | —OT elevated | 0.27% (19th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42965US | — | 0.27% (19th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42934US | — | 0.26% (18th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42975US | — | 0.26% (18th) | — | ✗no fix | 2025-08-12 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-43009US | —OT elevated | 0.26% (18th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-43007US | —OT elevated | 0.26% (18th) | — | ✗no fix | 2025-05-13 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42985US | — | 0.26% (17th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42962US | — | 0.25% (16th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42969US | — | 0.25% (16th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42986US | —OT elevated | 0.25% (16th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42981US | — | 0.24% (15th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |
| CVE-2025-42960US | —OT elevated | 0.23% (14th) | — | ✗no fix | 2025-07-08 | ≤ vers:unknown/bc-fes-gui8.00 |