totolink a3100r firmware
productUScpe:2.3:o:totolink:a3100r_firmware:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
21critical12high2medium0low
updated 2026-10-28
| 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-2022-25077US | critical9.8 | 30.4% (98th) | — | ✗no fix | 2022-02-24 | = 4.1.2cu.5050_b20200504 |
| CVE-2021-46009US | critical9.8OT elevated | 12.5% (96th) | — | ✗no fix | 2022-03-30 | = 5.9c.4577 |
| CVE-2024-7157US | high8.8 | 7.37% (94th) | — | ✗no fix | 2024-07-28 | = 4.1.2cu.5050_b20200504 |
| CVE-2022-26210US | critical9.8 | 5.69% (93rd) | — | ✗no fix | 2022-03-15 | = 4.1.2cu.5050_b20200504 |
| CVE-2021-46006US | medium6.5OT elevated | 5.50% (93rd) | — | ✗no fix | 2022-03-30 | = 5.9c.4577 |
| CVE-2022-28935US | high7.2 | 3.30% (88th) | — | ✗no fix | 2022-07-06 | = 4.1.2cu.5050_b20200504 |
| CVE-2024-7158US | high8.8 | 3.09% (88th) | — | ✗no fix | 2024-07-28 | = 4.1.2cu.5050_b20200504 |
| CVE-2022-26214US | critical9.8 | 2.78% (86th) | — | ✗no fix | 2022-03-15 | = 4.1.2cu.5050_b20200504 |
| CVE-2022-26212US | critical9.8 | 2.78% (86th) | — | ✗no fix | 2022-03-15 | = 4.1.2cu.5050_b20200504 |
| CVE-2022-26211US | critical9.8 | 2.78% (86th) | — | ✗no fix | 2022-03-15 | = 4.1.2cu.5050_b20200504 |
| CVE-2022-26208US | critical9.8 | 2.78% (86th) | — | ✗no fix | 2022-03-15 | = 4.1.2cu.5050_b20200504 |
| CVE-2021-44247US | critical9.8 | 2.78% (86th) | — | ✗no fix | 2022-02-04 | = 4.1.2cu.5050_b20200504 |
| CVE-2022-26209US | critical9.8 | 2.22% (83rd) | — | ✗no fix | 2022-03-15 | = 4.1.2cu.5050_b20200504 |
| CVE-2022-26207US | critical9.8 | 2.22% (83rd) | — | ✗no fix | 2022-03-15 | = 4.1.2cu.5050_b20200504 |
| CVE-2022-26206US | critical9.8 | 2.22% (83rd) | — | ✗no fix | 2022-03-15 | = 4.1.2cu.5050_b20200504 |
| CVE-2022-29639US | high8.1 | 1.83% (79th) | — | ✗no fix | 2022-05-18 | 2 versions |
| CVE-2022-29644US | critical9.8OT elevated | 1.60% (76th) | — | ✗no fix | 2022-05-18 | 2 versions |
| CVE-2022-29645US | critical9.8OT elevated | 1.47% (74th) | — | ✗no fix | 2022-05-18 | 2 versions |
| CVE-2025-28036US | — | 1.36% (72nd) | — | ✗no fix | 2025-04-22 | = 4.1.2cu.5247_b20211129 |
| CVE-2025-28035US | — | 1.36% (72nd) | — | ✗no fix | 2025-04-22 | = 4.1.2cu.5247_b20211129 |
| CVE-2025-28034US | — | 1.36% (72nd) | — | ✗no fix | 2025-04-22 | = 4.1.2cu.5247_b20211129 |
| CVE-2021-44620US | critical9.8 | 1.35% (71st) | — | ✗no fix | 2022-03-11 | ≤ 4.1.2cu.5050_b20200504 |
| CVE-2021-46010US | high8.8OT elevated | 1.24% (69th) | — | ✗no fix | 2022-03-30 | = 5.9c.4577 |
| CVE-2025-4496US | critical9.8 | 1.23% (69th) | — | ✗no fix | 2025-05-10 | = 4.1.8cu.5241_b20210927 |
| CVE-2022-29641US | high7.5 | 1.19% (68th) | — | ✗no fix | 2022-05-18 | 2 versions |
| CVE-2022-29643US | high7.5 | 1.18% (67th) | — | ✗no fix | 2022-05-18 | 2 versions |
| CVE-2022-29642US | high7.5 | 1.18% (67th) | — | ✗no fix | 2022-05-18 | 2 versions |
| CVE-2022-29640US | high7.5 | 1.18% (67th) | — | ✗no fix | 2022-05-18 | 2 versions |
| CVE-2022-29638US | high7.5 | 1.18% (67th) | — | ✗no fix | 2022-05-18 | 2 versions |
| CVE-2021-44246US | high7.5 | 1.18% (67th) | — | ✗no fix | 2022-02-04 | = 4.1.2cu.5050_b20200504 |
| CVE-2025-28256US | — | 0.97% (62nd) | — | ✗no fix | 2025-03-28 | = 4.1.2cu.5247_b20211129 |
| CVE-2021-46008US | high8.8OT elevated | 0.92% (60th) | — | ✗no fix | 2022-03-30 | = 5.9c.4577 |
| CVE-2022-29646US | medium5.3 | 0.84% (58th) | — | ✗no fix | 2022-05-18 | 2 versions |
| CVE-2025-45790US | critical9.8 | 0.82% (57th) | — | ✗no fix | 2025-05-08 | = 5.9c.1527 |
| CVE-2025-45789US | critical9.8 | 0.82% (57th) | — | ✗no fix | 2025-05-08 | = 5.9c.1527 |
| CVE-2025-45788US | critical9.8 | 0.82% (57th) | — | ✗no fix | 2025-05-08 | = 5.9c.1527 |
| CVE-2025-45787US | critical9.8 | 0.82% (57th) | — | ✗no fix | 2025-05-08 | = 5.9c.1527 |
| CVE-2024-36650US | — | 0.65% (51st) | — | ✗no fix | 2024-06-11 | = 4.1.2cu.5247_b20211129 |
| CVE-2024-42547US | critical9.8 | 0.63% (50th) | — | ✗no fix | 2024-08-12 | = 4.1.2cu.5050_b20200504 |
| CVE-2024-42546US | critical9.8 | 0.63% (50th) | — | ✗no fix | 2024-08-12 | = 4.1.2cu.5050_b20200504 |
| CVE-2025-28028US | — | 0.40% (34th) | — | ✗no fix | 2025-04-23 | = 4.1.2cu.5247_b20211129 |
| CVE-2025-28025US | — | 0.40% (34th) | — | ✗no fix | 2025-04-23 | = 4.1.2cu.5247_b20211129 |
| CVE-2025-28029US | — | 0.40% (34th) | — | ✗no fix | 2025-04-22 | = 4.1.2cu.5247_b20211129 |
| CVE-2025-28027US | — | 0.40% (34th) | — | ✗no fix | 2025-04-22 | = 4.1.2cu.5247_b20211129 |
| CVE-2025-28026US | — | 0.40% (34th) | — | ✗no fix | 2025-04-22 | = 4.1.2cu.5247_b20211129 |
| CVE-2025-28033US | — | 0.40% (34th) | — | ✗no fix | 2025-04-22 | = 4.1.2cu.5247_b20211129 |
| CVE-2025-28032US | — | 0.34% (28th) | — | ✗no fix | 2025-04-22 | = 4.1.2cu.5247_b20211129 |