Security readout for executives and security teams
Plain-English summary
CVE-2026-1410 affects Beetel 777VR1 broadband routers running firmware 01.00.09 or 01.00.09_55. The device UART interface reportedly lacks authentication, allowing a physically present attacker to access critical functions. Business urgency is moderate because exploitation requires physical device access and is described as difficult, but confidentiality, integrity, and availability impact can be high.
Executive priority
Treat this as a physical-access risk rather than a broad remote emergency. Prioritize affected routers in shared, public, branch, or customer-accessible locations. If no official fix is available, reduce physical access and plan replacement or compensating controls.
Technical view
The vulnerability is classified as missing authentication in the UART interface, mapped to CWE-287 and CWE-306. CVSS 3.1 is 6.4 with physical attack vector, high attack complexity, no privileges, no user interaction, and high C/I/A impact. VulDB states exploit material is public and the vendor did not respond to early disclosure.
Likely exposure
Exposure is mainly for organizations that deploy Beetel 777VR1 routers on affected firmware where attackers, insiders, contractors, or visitors could physically access devices. Remote internet exposure is not indicated by the provided sources.
Exploitation context
Sources state a public exploit exists, but exploitation requires physical access and is considered difficult. There is no KEV listing and no cited evidence of active exploitation in the wild.
Researcher notes
Evidence is limited to VulDB, the CVE record, and referenced public exploit material. The vulnerable UART function is not further specified in the provided bundle. Do not infer remote attackability or active exploitation. Vendor response and remediation status appear unresolved in the cited sources.
Mitigation direction
- Inventory Beetel 777VR1 routers and record firmware versions.
- Prioritize devices running 01.00.09 or 01.00.09_55.
- Check Beetel or service-provider guidance for firmware updates or official mitigation.
- Restrict physical access to routers, wiring closets, and customer-premises equipment.
- Use tamper controls or inspections where physical access cannot be tightly controlled.
- Consider replacement if no vendor-supported remediation is available.
Validation and detection
- Confirm model and firmware version through approved asset-management or device-administration processes.
- Review physical security around affected routers and UART-accessible areas.
- Check vendor, ISP, or procurement channels for updated firmware advisories.
- Look for unexplained device resets, configuration changes, or physical tampering signs.
- Document whether affected devices are in public, shared, or controlled locations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1410 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R0.55.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.4MediumVector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P/RL:X/RC:R
Source materials
- CVE List V5 sourceCVE List V5
- VDB-342799 | Beetel 777VR1 UART missing authenticationCVE reference · vdb-entry, technical-description
- VDB-342799 | CTI Indicators (IOB, IOC)CVE reference · signature, permissions-required
- Submit #739433 | Beetel Beetel 777VR1 Broadband Router Firmware Versions: V01.00.09 / V01.00.09_55 CWE-306 — Missing Authentication for Critical FunctionCVE reference · third-party-advisory
- https://gist.github.com/raghav20232023/96a6b13ab00c493d21362e744627ea9fCVE reference · exploit
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.