Security readout for executives and security teams
Plain-English summary
This CVE concerns Meatmeet devices reachable over Bluetooth Low Energy. A nearby unauthenticated person could make a device shut down, restart, or clear its configuration, causing service loss until it is turned back on, repaired, or reconfigured.
Executive priority
Treat as a moderate operational risk for environments relying on Meatmeet device availability. Prioritize if devices are deployed in shared, public, or physically accessible spaces.
Technical view
CVE-2025-65828 is a CWE-306 missing-authentication issue. BLE commands such as shutdown, restart, and clear config can be issued without authentication by an adjacent attacker, impacting availability only. The CVSS 3.1 score is 6.5 with adjacent-network attack vector and high availability impact.
Likely exposure
Exposure appears limited to Meatmeet devices within BLE proximity of an attacker. The source bundle does not provide vendor, product version, firmware, or CPE details, so precise asset matching is incomplete.
Exploitation context
The CVE source states exploitation requires proximity to the device over BLE. KEV is false, and the supplied sources do not report active exploitation or public weaponized exploitation.
Researcher notes
The record names Meatmeet behavior but affected vendor, product, version, and CPE fields are unavailable. Analysis should avoid broad matching until vendor or CVE metadata clarifies affected models and fixed versions.
Mitigation direction
- Check Meatmeet or vendor guidance for firmware updates or official mitigations.
- Limit physical proximity to deployed Meatmeet devices, especially in public or visitor-accessible areas.
- Monitor for unexpected shutdowns, restarts, configuration resets, or loss of base-station updates.
- Prepare reconfiguration procedures for devices disassociated from their user.
Validation and detection
- Inventory any Meatmeet devices and their deployment locations.
- Confirm whether devices are reachable by BLE from uncontrolled areas.
- Review operational logs or alerts for unexpected resets or cloud update loss.
- Verify recovery steps for devices after clear-configuration events.
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-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-2025-65828 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.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
SSVC decision data
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:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H2.83.6CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://gist.github.com/dead1nfluence/4dffc239b4a460f41a03345fd8e5feb5#file-denial-of-service-ble-mdCVE reference, mitre
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.
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.