CVE-2026-20766
Out-of-bounds memory access in Milesight AIOT camera firmware (CWE-122)
Is CVE-2026-20766 being exploited?
Not confirmed. CVE-2026-20766 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-20766?
CVE-2026-20766 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-20766?
Not known from our data. No patch reference has been recorded for CVE-2026-20766, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-20766 affect?
CVE-2026-20766 affects Milesight AIOT camera firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-20766?
Patch firmware when released; monitor for updates.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Memory corruption via out-of-bounds access could crash or enable arbitrary code execution.
Patch when possible
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= 62.8.0.4-r5
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= 63.8.0.4-r3
- affected<= 48.8.0.4-r3
- affected<= CQ_63.8.0.5-r1
- affected<= CQ_63.8.0.5-r1
- affected<= CQ_63.8.0.5-r1
- affected<= 61.8.0.5-r2
- affected<= 61.8.0.5-r2
- affected<= 61.8.0.5-r2
- affected<= 63.8.0.5-r3
- affected<= 61.8.0.5-r2
- affected<= 51.7.0.77-r12
- affected<= 51.7.0.77-r12
- affected<= 61.8.0.5-r2
- affected<= 63.8.0.4-r1-NX
- affected<= 63.8.0.4-r1-NX
- affected<= 63.8.0.5-r3
- affected<= 61.8.0.5-r2
- affected<= 61.8.0.5-r2
- affected<= 45.8.0.2-AIoT-r4
- affected<= 61.8.0.5-r2
- affected<= 61.8.0.5-r2
- affected<= 63.8.0.4-r1-NX
- affected<= 63.8.0.4-r1-NX
- affected<= 63.8.0.5-r3
- affected<= 61.8.0.5-r2
- affected<= 51.7.0.77-r12
- affected<= 3x.8.0.3-r11
- affected<= 51.7.0.77-r12
- affected<= 61.8.0.5-r2
- affected<= 51.7.0.77-r12
- affected<= 7x.9.0.19-r5
- affected<= 7x.9.0.19-r5
- affected<= 7x.9.0.19-r5
- affected<= 7x.9.0.19-r5
- affected<= 7x.9.0.19-r5
- affected<= 7x.9.0.19-r5
- affected<= PI_61.8.0.3_LPR-r3
- affected<= PO_61.8.0.4_LPR
- affected<= PO_61.8.0.4_LPR
- affected<= C_21.1.0.8-r4
- affected<= 52.8.0.4-r5
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= T_45.8.0.3-r9
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_63.8.0.4_LPR-r3
- affected<= T_63.8.0.4_LPR-r3
- affected<= T_63.8.0.4_LPR-r3
- affected<= T_63.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_63.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_47.8.0.4_LPR-r6
- affected<= T_47.8.0.4_LPR-r7
- affected<= T_47.8.0.4_LPR-r6
- affected<= T_45.8.0.3-r9
- affected<= T_63.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_63.8.0.4_LPR-r3
- affected<= T_63.8.0.4_LPR-r3
- affected<= T_63.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
- affected<= T_61.8.0.4_LPR-r3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.