totolink t6 firmware
productUScpe:2.3:o:totolink:t6_firmware:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
15critical16high1medium0low
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-2025-6916US | —OT elevated | 0.89% (59th) | Exploit | ✗no fix | 2025-06-30 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7952US | high8.8 | 24.5% (98th) | — | ✗no fix | 2025-07-22 | = v4.1.5cu.748_b20211015 |
| CVE-2022-25084US | critical9.8 | 21.8% (98th) | — | ✗no fix | 2022-02-24 | = 5.9c.4085_b20190428 |
| CVE-2022-38828US | critical9.8 | 20.1% (97th) | — | ✗no fix | 2022-09-16 | = 4.1.5cu.709_b20210518 |
| CVE-2022-38827US | critical9.8 | 12.5% (96th) | — | ✗no fix | 2022-09-16 | = 4.1.5cu.709_b20210518 |
| CVE-2022-25134US | critical9.8 | 2.99% (87th) | — | ✗no fix | 2022-02-19 | = v4.1.5cu.748_b20211015 |
| CVE-2022-25135US | critical9.8 | 2.93% (87th) | — | ✗no fix | 2022-02-19 | = v4.1.5cu.748_b20211015 |
| CVE-2022-25133US | critical9.8 | 2.91% (87th) | — | ✗no fix | 2022-02-19 | = v4.1.5cu.748_b20211015 |
| CVE-2022-25132US | critical9.8 | 2.91% (87th) | — | ✗no fix | 2022-02-19 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7525US | high8.8 | 2.83% (87th) | — | ✗no fix | 2025-07-13 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7524US | high8.8 | 2.83% (87th) | — | ✗no fix | 2025-07-13 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7615US | high8.8 | 2.38% (84th) | — | ✗no fix | 2025-07-14 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7614US | high8.8 | 2.38% (84th) | — | ✗no fix | 2025-07-14 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7613US | high8.8 | 2.38% (84th) | — | ✗no fix | 2025-07-14 | = v4.1.5cu.748_b20211015 |
| CVE-2022-25137US | critical9.8 | 2.20% (82nd) | — | ✗no fix | 2022-02-19 | = v4.1.5cu.748_b20211015 |
| CVE-2022-25136US | critical9.8 | 2.20% (82nd) | — | ✗no fix | 2022-02-19 | = v4.1.5cu.748_b20211015 |
| CVE-2022-25131US | critical9.8 | 2.20% (82nd) | — | ✗no fix | 2022-02-19 | = v4.1.5cu.748_b20211015 |
| CVE-2022-25130US | critical9.8 | 2.20% (82nd) | — | ✗no fix | 2022-02-19 | = v4.1.5cu.748_b20211015 |
| CVE-2023-7221US | critical9.8 | 1.52% (74th) | — | ✗no fix | 2024-01-09 | = 4.1.9cu.5241_b20210923 |
| CVE-2022-38826US | critical9.8 | 1.31% (71st) | — | ✗no fix | 2022-09-16 | = 4.1.5cu.709_b20210518 |
| CVE-2025-8170US | — | 1.31% (70th) | — | ✗no fix | 2025-07-25 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7837US | — | 1.28% (70th) | — | ✗no fix | 2025-07-19 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7912US | — | 1.28% (70th) | — | ✗no fix | 2025-07-20 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7862US | critical9.8OT elevated | 1.21% (68th) | — | ✗no fix | 2025-07-20 | = v4.1.5cu.748_b20211015 |
| CVE-2022-32044US | high7.5 | 1.15% (67th) | — | ✗no fix | 2022-07-01 | = 4.1.9cu.5179_b20201015 |
| CVE-2022-32053US | high7.5 | 1.14% (66th) | — | ✗no fix | 2022-07-01 | = 4.1.9cu.5179_b20201015 |
| CVE-2022-32052US | high7.5 | 1.14% (66th) | — | ✗no fix | 2022-07-01 | = 4.1.9cu.5179_b20201015 |
| CVE-2022-32051US | high7.5 | 1.14% (66th) | — | ✗no fix | 2022-07-01 | = 4.1.9cu.5179_b20201015 |
| CVE-2022-32050US | high7.5 | 1.14% (66th) | — | ✗no fix | 2022-07-01 | = 4.1.9cu.5179_b20201015 |
| CVE-2022-32049US | high7.5 | 1.14% (66th) | — | ✗no fix | 2022-07-01 | = 4.1.9cu.5179_b20201015 |
| CVE-2022-32048US | high7.5 | 1.14% (66th) | — | ✗no fix | 2022-07-01 | = 4.1.9cu.5179_b20201015 |
| CVE-2022-32047US | high7.5 | 1.14% (66th) | — | ✗no fix | 2022-07-01 | = 4.1.9cu.5179_b20201015 |
| CVE-2022-32046US | high7.5 | 1.14% (66th) | — | ✗no fix | 2022-07-01 | = 4.1.9cu.5179_b20201015 |
| CVE-2022-32045US | high7.5 | 1.14% (66th) | — | ✗no fix | 2022-07-01 | = 4.1.9cu.5179_b20201015 |
| CVE-2022-38823US | critical9.8OT elevated | 1.10% (66th) | — | ✗no fix | 2022-09-16 | = 4.1.5cu.709_b20210518 |
| CVE-2025-7913US | — | 0.99% (62nd) | — | ✗no fix | 2025-07-21 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7758US | — | 0.99% (62nd) | — | ✗no fix | 2025-07-17 | = v4.1.5cu.748_b20211015 |
| CVE-2025-7460US | — | 0.96% (61st) | — | ✗no fix | 2025-07-11 | = v4.1.5cu.748_b20211015 |
| CVE-2023-7223US | medium6.5 | 0.64% (51st) | — | ✗no fix | 2024-01-09 | = 4.1.9cu.5241_b20210923 |