# CVE-2026-29115: Denial of service in IPC/SD

> An authenticated remote attacker can cause a system reboot and denial of service in Dahua IP cameras by sending a specially crafted packet.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-8v9p-fgh7-hrp2

## What is CVE-2026-29115?

CVE-2026-29115 is a medium-severity denial of service vulnerability in Dahua IPC/SD, published on 10 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability has been found in some Dahua products could allow an authenticated remote attacker to send a specially crafted packet, triggering an exception that causes the system to reboot unexpectedly, resulting in a denial of service.

Weakness: CWE-617 (Reachable Assertion)

## Which versions are affected by CVE-2026-29115?


## How do I fix CVE-2026-29115?

No fix has been published for CVE-2026-29115 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-29115 being exploited?

There is no known exploitation of CVE-2026-29115 in the wild and no public exploit code.

Public exploit code:

- Dahua CVE-2026-29115 (github_poc): https://github.com/CrimsonfiedOfficial/CVE-2026-29115

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29115 and fix it if it is affected.

What it is: CVE-2026-29115 is a medium-severity denial of service vulnerability in Dahua IPC/SD, published on 10 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29115 in the wild and no public exploit code.

Affected product: Dahua IPC/SD. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29115/ (Markdown: https://insights.sbomify.com/CVE-2026-29115/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29115
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29115
- OSV: https://osv.dev/vulnerability/CVE-2026-29115

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29115/
Summaries are generated and may contain mistakes; the official description above is the record.