CVE Intelligence
Medium Info disclosure exploit reference

CVE-2026-1407 — Beetel 777VR1 UART information disclosure

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.

Published Jan 25, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.3% (30-day exploitation probability)+3
  • Technical severity (medium)+3
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.3%
ahead of 21% of scored CVEs · Oct 14, 2026
Affects
Beetel
777VR1 and 1 more
CVSS base
4.2
Medium · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Beetel 777VR1, Beetel 777vr1 Firmware).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Beetel 777VR1 version 01.00.09version 01.00.09_55 Vulnerable CVE Program (cve.org) e CISA ADP
Beetel 777vr1 Firmware ≤ 01.00.09_55 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Physical
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
1.0 CVSS 4.0 Low — — VulDB via CVE Program (cve.org) e CISA ADP
0.3 CVSS 4.0 Low — — cna@vuldb.com via NIST National Vulnerability Database
4.2 CVSS 3.1 Medium 0.5 3.6 nvd@nist.gov via NIST National Vulnerability Database
2.0 CVSS 3.1 Low 0.5 1.4 cna@vuldb.com via NIST National Vulnerability Database
2.0 CVSS 3.1 Low — — VulDB via CVE Program (cve.org) e CISA ADP
2.0 CVSS 3.0 Low — — VulDB via CVE Program (cve.org) e CISA ADP
1.2 CVSS 2.0 Low 1.9 2.9 cna@vuldb.com via NIST National Vulnerability Database
1.2 CVSS 2.0 Low — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 4.2 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.30%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Look for anomalous data read/export volumes and access to sensitive records.
endpoint telemetry (EDR)application logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · beetel/777vr1
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 4.2
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Jan 25, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

  • vuldb.com/
    Permissions Required, VDB Entry, signature, permissions-required, NIST National Vulnerability Database
  • gist.github.com/raghav20232023/253c041842f622d9c2cb6ee4111c2227
    Exploit, Third Party Advisory, exploit, NIST National Vulnerability Database
  • vuldb.com/
    Third Party Advisory, VDB Entry, third-party-advisory, NIST National Vulnerability Database
  • vuldb.com/
    Third Party Advisory, VDB Entry, vdb-entry, technical-description, NIST National Vulnerability Database

Elsewhere on this site

Beetel
every CVE for this vendor
Info disclosure
same class
CWE-200
other pages naming this weakness

Related CVEs (same products)

  • Low CVE-2026-2702 Beetel 777VR1 WPA2 PSK hard-coded credentials Feb 19, 2026
  • High CVE-2026-2618 Beetel 777VR1 SSH Service risky encryption Feb 17, 2026
  • High CVE-2026-2617 Beetel 777VR1 Telnet Service/SSH Service insecure default initialization of resource Feb 17, 2026
  • Critical CVE-2026-2616 Beetel 777VR1 Web Management hard-coded credentials Feb 17, 2026
  • Medium CVE-2026-1411 Beetel 777VR1 UART access control Jan 25, 2026
  • Medium CVE-2026-1410 Beetel 777VR1 UART missing authentication Jan 25, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-1407 is "Beetel 777VR1 UART information disclosure", rated Medium. It affects 777VR1 (Beetel); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.2 describes technical severity. EPSS 0.30% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.