Adjacent traffic decryption via weak AES key
Published Jan 29, 2026 · Updated Jan 29, 2026
Weak web-interface encryption in TP-Link VX800v v1.0 firmware before 800.0.11 allows adjacent attackers to decrypt intercepted traffic. The web interface encrypts traffic with an AES key weak enough to brute-force, allowing captured ciphertext to be recovered without authentication. Exploitation requires network proximity and traffic interception, with consequences confined to transmitted data.
Summary
What happened
Weak web-interface encryption in TP-Link VX800v v1.0 firmware before 800.0.11 allows adjacent attackers to decrypt intercepted traffic. The web interface encrypts traffic with an AES key weak enough to brute-force, allowing captured ciphertext to be recovered without authentication. Exploitation requires network proximity and traffic interception, with consequences confined to transmitted data.
The record
- CVE
- CVE-2025-13399
- Published
- Jan 29, 2026
- Updated
- Jan 29, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- VX800v
- Classifications
- CWE-331, T1040
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 29, 2026CVE publishedPublication date reported by the CVE source.
- Jan 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <800.0.11 (0.11.0 3.0.0 v603c.0 Build 250702)
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo