Device compromise via unrestricted UART bootloader commands
Published Jan 26, 2026 · Updated Jan 26, 2026
UART bootloader access-control failure in Beetel 777VR1 01.00.09 and 01.00.09_55 allows physically proximate attackers to read and modify memory. The production bootloader exposes functional memory-read, memory-write, dump, and TFTP backup commands without lifecycle or operating-mode restrictions. Reaching the commands requires physical UART access and interrupting startup with ESC; they permit firmware extraction, arbitrary memory or flash modification, and persistent malicious code.
Summary
What happened
UART bootloader access-control failure in Beetel 777VR1 01.00.09 and 01.00.09_55 allows physically proximate attackers to read and modify memory. The production bootloader exposes functional memory-read, memory-write, dump, and TFTP backup commands without lifecycle or operating-mode restrictions. Reaching the commands requires physical UART access and interrupting startup with ESC; they permit firmware extraction, arbitrary memory or flash modification, and persistent malicious code.
The record
- CVE
- CVE-2026-1411
- Published
- Jan 26, 2026
- Updated
- Jan 26, 2026
- Vendor
- Beetel Teletech Limited
- Product
- 777VR1 Firmware
- Classifications
- CWE-266, CWE-284, T1542.001
- Attack vector
- physical
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 26, 2026CVE publishedPublication date reported by the CVE source.
- Jan 26, 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=01.00.09
- Affected versionversion=01.00.09_55
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.
Weakness, pattern, technique
Public exploit references
- Excessive Bootloader Functionality Exposed in Production Firmwareproof of concept · demonstrated
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