CVE-2026-91138
What it is
The Deco BE65 v3 firmware contains a shared hard-coded password hash for the root account in /etc/shadow. Where the corresponding credential is accepted by a production authentication path, an attacker with existing unprivileged shell access may recover or otherwise obtain the plaintext password and use it to escalate privileges. Successful exploitation may grant root-level access to the affected device.
At a glance
- Exploitability
- Can be exploited with physical access with a low-privilege account. High risk of data exposure, data tampering, service disruption.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- ReservedThe CVE id was reserved by its CNA
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: not scored yet.
- Severity: 6.9 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Weakness
- CWE-798 · Hard-coded credentials
- Record status
- Received
Affected
- TP-Link Systems Inc. Deco BE65 v3 < 1.0.11 Build 26092212 Rel. 18351
Attack profile CVSS 4.0 · 6.9
- Attack vector
- Physical
- Complexity
- Low
- Attack requirements
- Present
- Privileges needed
- Low
- User interaction
- None
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:4.0/AV:P/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:L/SA:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-91138.md and follow it. Check whether this project is affected by CVE-2026-91138. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://www.tp-link.com/en/support/download/deco-be65/v3/
- https://www.tp-link.com/kr/support/download/deco-be65/v3/
- https://www.tp-link.com/us/support/faq/5414/