# CVE-2025-56801: Hardcoded credentials in n/a

> Attackers with local access can decrypt configuration data due to a hardcoded initialization vector in the Reolink Desktop Application.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2025
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-38fr-2xrg-mwqm

## What is CVE-2025-56801?

CVE-2025-56801 is a medium-severity vulnerability in n/a, published on 21 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Reolink Desktop Application 8.18.12 contains hardcoded credentials as the Initialization Vector (IV) in its AES-CFB encryption implementation allowing attackers with access to the application environment to reliably decrypt encrypted configuration data. NOTE: the Supplier's position is that material is not hardcoded and is instead randomly generated on each installation of the application.

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

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

It affects 1 product.


Products: Reolink Reolink.

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

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

## Is CVE-2025-56801 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56801 exists.

Public exploit code:

- AES-CFB IV Generation Vulnerability in Reolink Desktop Application (github_poc): https://github.com/shinyColumn/CVE-2025-56801

## Other vulnerabilities in n/a

- [CVE-2025-55619](https://insights.sbomify.com/CVE-2025-55619/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-56799](https://insights.sbomify.com/CVE-2025-56799/): Command injection in n/a (medium 6.5)
- [CVE-2025-55621](https://insights.sbomify.com/CVE-2025-55621/): Information disclosure in n/a (medium 6.5)
- [CVE-2025-55622](https://insights.sbomify.com/CVE-2025-55622/): Other in n/a (medium 6.5)
- [CVE-2025-55625](https://insights.sbomify.com/CVE-2025-55625/): Open redirect in n/a (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56801 is a medium-severity vulnerability in n/a, published on 21 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56801 exists.

Affected product: n/a. 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-56801/ (Markdown: https://insights.sbomify.com/CVE-2025-56801/index.md)
```

## Sources

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

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