reolink rlc-410w firmware
productUScpe:2.3:o:reolink:rlc-410w_firmware:*:*:*:*:*:*:*:*
A product tracked in the threat graph; the vulnerabilities below are known to affect it.
by severity
3critical81high4medium0low
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-2021-40407US | high7.2OT critical | 47.6% (99th) | KEV | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2019-11001US | high7.2OT critical | 37.5% (99th) | KEV | ✗no fix | 2019-04-08 | ≤ 1.0.227 |
| CVE-2021-40410US | high7.2 | 27.9% (98th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-40412US | high7.2 | 27.5% (98th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-40411US | high7.2 | 4.70% (92nd) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-40409US | critical9.8 | 3.66% (90th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-40408US | critical9.8 | 3.66% (90th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2022-21236US | high7.5 | 1.81% (79th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44394US | high7.5 | 1.80% (78th) | — | ✗no fix | 2022-04-14 | = 3.0.0.136_20121102 |
| CVE-2021-44375US | high7.5 | 1.80% (78th) | — | ✗no fix | 2022-04-14 | = 3.0.0.136_20121102 |
| CVE-2021-44366US | high7.5 | 1.80% (78th) | — | ✗no fix | 2022-04-14 | = 3.0.0.136_20121102 |
| CVE-2021-44357US | high7.5 | 1.80% (78th) | — | ✗no fix | 2022-04-14 | = 3.0.0.136_20121102 |
| CVE-2021-44356US | high7.5 | 1.80% (78th) | — | ✗no fix | 2022-04-14 | = 3.0.0.136_20121102 |
| CVE-2021-44355US | high7.5 | 1.80% (78th) | — | ✗no fix | 2022-04-14 | = 3.0.0.136_20121102 |
| CVE-2021-44354US | high7.5 | 1.80% (78th) | — | ✗no fix | 2022-04-14 | = 3.0.0.136_20121102 |
| CVE-2021-40406US | high7.5 | 1.53% (75th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-40423US | high7.5 | 1.34% (71st) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-40419US | high7.5OT elevated | 1.23% (69th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-40404US | medium6.5 | 1.23% (69th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2022-21217US | critical9.8 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44419US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44418US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44417US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44416US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44415US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44414US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44413US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44412US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44411US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44410US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44409US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44408US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44407US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44406US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44405US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44404US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44403US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44402US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44401US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44400US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44399US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44398US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44397US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44396US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44395US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44393US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44392US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44391US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44390US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
| CVE-2021-44389US | high7.7 | 1.21% (68th) | — | ✗no fix | 2022-01-28 | = 3.0.0.136_20121102 |
showing 50 of 88