# CVE-2025-52601: Hardcoding sensitive information

> An attacker can decrypt sensitive information using a hardcoded encryption key in Hanwha Vision Device Manager, requiring a firmware patch.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Dec 2025
- **Updated:** 26 Dec 2025
- **Also known as:** GHSA-7954-xqv5-fh2r

## What is CVE-2025-52601?

CVE-2025-52601 is a medium-severity vulnerability in Hanwha Vision Co., Ltd. Device Manager, published on 26 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cybersecurity Nozomi Networks Labs, a specialized security company focused on Industrial Control Systems (ICS) and OT/IoT security, has discovered a vulnerability in Device Manager that a hardcoded encryption key for sensitive information. An attacker can use key to decrypt sensitive information. The manufacturer has released patch firmware for the flaw, please refer to the manufacturer's report for details and workarounds.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2025-52601?

It affects 256 products.


Products: Hanwhavision Knb-2000 Firmware, Hanwhavision Knb-5000n Firmware, Hanwhavision Knd-2010 Firmware, Hanwhavision Knd-2020rn Firmware, Hanwhavision Knd-2080rn Firmware, Hanwhavision Knd-5020rn Firmware, Hanwhavision Knd-5080rn Firmware, Hanwhavision Kno-2010rn Firmware, Hanwhavision Kno-2080rn Firmware, Hanwhavision Kno-2120rn Firmware, Hanwhavision Kno-5020rn Firmware, Hanwhavision Kno-5080rn Firmware, Hanwhavision Knp-2120hn Firmware, Hanwhavision Knp-2320rh Firmware, Hanwhavision Knp-2320rha Firmware, Hanwhavision Knp-2550rha Firmware, Hanwhavision Pnm-7000vd Firmware, Hanwhavision Pnm-7002vd Firmware, Hanwhavision Pnm-9000vd Firmware, Hanwhavision Pnm-9000vq Firmware and 236 more.

## How do I fix CVE-2025-52601?

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

## Is CVE-2025-52601 being exploited?

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

## Other vulnerabilities in Hanwha Vision Co., Ltd. Device Manager

- [CVE-2024-54013](https://insights.sbomify.com/CVE-2024-54013/): Authentication Bypass (high 8.7)
- [CVE-2024-54012](https://insights.sbomify.com/CVE-2024-54012/): Command Injection (high 8.5)
- [CVE-2025-52598](https://insights.sbomify.com/CVE-2025-52598/): Insufficient certificate validation (medium 6.3)
- [CVE-2025-52599](https://insights.sbomify.com/CVE-2025-52599/): Inadequate account permissions management (medium 6.3)
- [CVE-2025-8075](https://insights.sbomify.com/CVE-2025-8075/): Improper Input Validation (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-52601 and fix it if it is affected.

What it is: CVE-2025-52601 is a medium-severity vulnerability in Hanwha Vision Co., Ltd. Device Manager, published on 26 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52601 in the wild and no public exploit code.

Affected product: Hanwha Vision Co., Ltd. Device Manager. 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-2025-52601/ (Markdown: https://insights.sbomify.com/CVE-2025-52601/index.md)
```

## Sources

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

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