# CVE-2026-61390: Memory corruption in DS-2CD Series

> Unauthenticated attackers can cause device malfunction via heap buffer overflow in Hikvision cameras by sending crafted packets.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-739w-7wq3-9vff

## What is CVE-2026-61390?

CVE-2026-61390 is a high-severity memory corruption vulnerability in Hikvision DS-2CD Series, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

There is a heap buffer overflow vulnerability in some Hikvision cameras, which may allow unauthenticated attackers to cause device malfunction by sending specially crafted packets.

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

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

## Is CVE-2026-61390 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61390 is a high-severity memory corruption vulnerability in Hikvision DS-2CD Series, published on 22 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-61390 in the wild and no public exploit code.

Affected product: Hikvision DS-2CD Series. 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-61390/ (Markdown: https://insights.sbomify.com/CVE-2026-61390/index.md)
```

## Sources

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

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