totolink a3300r firmware
productUScpe:2.3:o:totolink:a3300r_firmware:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
26critical9high1medium0low
updated 2026-10-29
| 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-24329US | critical9.8 | 6.17% (93rd) | — | ✗no fix | 2024-01-30 | = 17.0.0cu.557_b20221024 |
| CVE-2024-24328US | critical9.8 | 6.17% (93rd) | — | ✗no fix | 2024-01-30 | = 17.0.0cu.557_b20221024 |
| CVE-2025-52046US | critical9.8 | 5.31% (93rd) | — | ✗no fix | 2025-07-17 | = 17.0.0cu.596_b20250515 |
| CVE-2026-5178US | high8.8 | 4.10% (91st) | — | ✗no fix | 2026-03-31 | = 17.0.0cu.557_b20221024 |
| CVE-2026-5105US | high8.8 | 4.07% (91st) | — | ✗no fix | 2026-03-30 | = 17.0.0cu.557_b20221024 |
| CVE-2026-5103US | high8.8 | 4.07% (91st) | — | ✗no fix | 2026-03-30 | = 17.0.0cu.557_b20221024 |
| CVE-2026-5104US | high8.8 | 2.78% (86th) | — | ✗no fix | 2026-03-30 | = 17.0.0cu.557_b20221024 |
| CVE-2026-5177US | high8.8 | 2.74% (86th) | — | ✗no fix | 2026-03-31 | = 17.0.0cu.557_b20221024 |
| CVE-2026-5101US | high8.8 | 2.44% (84th) | — | ✗no fix | 2026-03-29 | = 17.0.0cu.557_b20221024 |
| CVE-2026-5102US | high8.8 | 2.42% (84th) | — | ✗no fix | 2026-03-30 | = 17.0.0cu.557_b20221024 |
| CVE-2026-5176US | critical9.8 | 2.16% (82nd) | — | ✗no fix | 2026-03-31 | = 17.0.0cu.557_b20221024 |
| CVE-2023-37173US | critical9.8 | 1.96% (80th) | — | ✗no fix | 2023-07-07 | = 17.0.0cu.557_b20221024 |
| CVE-2023-37172US | critical9.8 | 1.96% (80th) | — | ✗no fix | 2023-07-07 | = 17.0.0cu.557_b20221024 |
| CVE-2023-37171US | critical9.8 | 1.96% (80th) | — | ✗no fix | 2023-07-07 | = 17.0.0cu.557_b20221024 |
| CVE-2024-24332US | critical9.8 | 1.73% (78th) | — | ✗no fix | 2024-01-30 | = 17.0.0cu.557_b20221024 |
| CVE-2024-24325US | critical9.8 | 1.73% (78th) | — | ✗no fix | 2024-01-30 | = 17.0.0cu.557_b20221024 |
| CVE-2024-23061US | critical9.8 | 1.73% (77th) | — | ✗no fix | 2024-01-11 | = 17.0.0cu.557_b20221024 |
| CVE-2024-23059US | critical9.8 | 1.73% (77th) | — | ✗no fix | 2024-01-11 | = 17.0.0cu.557_b20221024 |
| CVE-2024-24333US | critical9.8 | 1.70% (77th) | — | ✗no fix | 2024-01-30 | = 17.0.0cu.557_b20221024 |
| CVE-2024-23060US | critical9.8 | 1.70% (77th) | — | ✗no fix | 2024-01-11 | = 17.0.0cu.557_b20221024 |
| CVE-2023-37170US | critical9.8 | 1.68% (77th) | — | ✗no fix | 2023-07-07 | = 17.0.0cu.557_b20221024 |
| CVE-2024-24327US | critical9.8 | 1.64% (76th) | — | ✗no fix | 2024-01-30 | = 17.0.0cu.557_b20221024 |
| CVE-2024-24326US | critical9.8 | 1.64% (76th) | — | ✗no fix | 2024-01-30 | = 17.0.0cu.557_b20221024 |
| CVE-2024-23058US | critical9.8 | 1.64% (76th) | — | ✗no fix | 2024-01-11 | = 17.0.0cu.557_b20221024 |
| CVE-2024-23057US | critical9.8 | 1.64% (76th) | — | ✗no fix | 2024-01-11 | = 17.0.0cu.557_b20221024 |
| CVE-2024-22942US | critical9.8 | 1.64% (76th) | — | ✗no fix | 2024-01-11 | = 17.0.0cu.557_b20221024 |
| CVE-2024-24331US | critical9.8 | 1.62% (76th) | — | ✗no fix | 2024-01-30 | = 17.0.0cu.557_b20221024 |
| CVE-2024-24330US | critical9.8 | 1.52% (74th) | — | ✗no fix | 2024-01-30 | = 17.0.0cu.557_b20221024 |
| CVE-2023-46993US | critical9.8 | 1.52% (74th) | — | ✗no fix | 2023-10-31 | = 17.0.0cu.557_b20221024 |
| CVE-2023-46976US | critical9.8 | 1.52% (74th) | — | ✗no fix | 2023-10-31 | = 17.0.0cu.557_b20221024 |
| CVE-2024-27521US | — | 1.50% (74th) | — | ✗no fix | 2024-03-26 | = 17.0.0cu.557_b20221024 |
| CVE-2023-31729US | critical9.8 | 1.34% (71st) | — | ✗no fix | 2023-05-18 | = 17.0.0cu.557 |
| CVE-2024-7331US | high8.8 | 1.20% (68th) | — | ✗no fix | 2024-08-01 | = 17.0.0cu.557_b20221024 |
| CVE-2025-55901US | — | 1.10% (66th) | — | ✗no fix | 2025-12-15 | = 17.0.0cu.596_b20250515 |
| CVE-2025-12241US | — | 1.03% (64th) | — | ✗no fix | 2025-10-27 | = 17.0.0cu.557_b20221024 |
| CVE-2025-12260US | — | 1.02% (63rd) | — | ✗no fix | 2025-10-27 | = 17.0.0cu.557_b20221024 |
| CVE-2025-12259US | — | 1.02% (63rd) | — | ✗no fix | 2025-10-27 | = 17.0.0cu.557_b20221024 |
| CVE-2025-12258US | — | 1.02% (63rd) | — | ✗no fix | 2025-10-27 | = 17.0.0cu.557_b20221024 |
| CVE-2025-12240US | critical9.8 | 0.84% (58th) | — | ✗no fix | 2025-10-27 | = 17.0.0cu.557_b20221024 |
| CVE-2025-12239US | critical9.8 | 0.84% (58th) | — | ✗no fix | 2025-10-27 | = 17.0.0cu.557_b20221024 |
| CVE-2026-31177US | — | 0.60% (49th) | — | ✗no fix | 2026-04-23 | = 17.0.0cu.557_b20221024 |
| CVE-2026-31181US | — | 0.58% (47th) | — | ✗no fix | 2026-04-23 | = 17.0.0cu.557_b20221024 |
| CVE-2026-31178US | — | 0.58% (47th) | — | ✗no fix | 2026-04-23 | = 17.0.0cu.557_b20221024 |
| CVE-2026-31175US | — | 0.58% (47th) | — | ✗no fix | 2026-04-23 | = 17.0.0cu.557_b20221024 |
| CVE-2026-31170US | — | 0.57% (47th) | — | ✗no fix | 2026-04-09 | = 17.0.0cu.557_b20221024 |
| CVE-2023-46992US | high7.5OT elevated | 0.54% (45th) | — | ✗no fix | 2023-10-31 | = 17.0.0cu.557_b20221024 |
| CVE-2025-55895US | — | 0.34% (27th) | — | ✗no fix | 2025-12-15 | = 17.0.0cu.557_b20221024 |
| CVE-2026-31173US | — | 0.28% (20th) | — | ✗no fix | 2026-04-23 | = 17.0.0cu.557_b20221024 |
| CVE-2026-31169US | — | 0.28% (20th) | — | ✗no fix | 2026-04-23 | = 17.0.0cu.557_b20221024 |
| CVE-2026-31168US | — | 0.28% (20th) | — | ✗no fix | 2026-04-23 | = 17.0.0cu.557_b20221024 |
showing 50 of 64