Skip to content
IoT

CVE-2026-29116

8.7
High
EPSS 0.40%Jun 10, 2026

Unauthenticated remote DoS reboot in Dahua devices

common questions

Is CVE-2026-29116 being exploited?

Not confirmed. CVE-2026-29116 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.40% probability of exploitation in the next 30 days.

How severe is CVE-2026-29116?

CVE-2026-29116 is rated High with a CVSS score of 8.7. 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-29116?

Not known from our data. No patch reference has been recorded for CVE-2026-29116, 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-29116 affect?

CVE-2026-29116 affects Dahua surveillance devices, Dahua IP cameras, Dahua NVRs. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-29116?

Apply firmware updates when released; monitor affected devices

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Dahua surveillance devicesDahua IP camerasDahua NVRs
impact

Unauthenticated attacker can reboot Dahua devices via crafted packet, causing DoS and downtime.

action required

Patch when possible

affected versions
Dahua IPC/SD/NVR/XVR/EVS/VTO/VTH/ASI/TPC
  • affectedAffected products are limited to certain models of IPC, SD, NVR, XVR, EVS, VTO, VTH, ASI, and TPC devices with versions built before March 26, 2026.

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free