Security readout for executives and security teams
Plain-English summary
This CVE affects Bluetooth Mesh provisioning. A nearby attacker may authenticate as part of provisioning if the setup value is not random enough and can be brute-forced before provisioning times out. The business risk is unauthorized mesh enrollment during setup, not a confirmed internet-scale compromise.
Executive priority
Treat as targeted operational risk for Bluetooth Mesh environments. Prioritize teams managing building systems, IoT fleets, or industrial mesh deployments, especially where provisioning occurs in shared or public spaces.
Technical view
Bluetooth Mesh Profile 1.0 and 1.0.1 provisioning can be exposed when AuthValue entropy is insufficient. A nearby device may use a brute-force attempt and malleable commitment behavior to complete authentication before timeout. The provided sources do not identify specific vendors, products, CVSS, or a confirmed patch.
Likely exposure
Organizations using Bluetooth Mesh devices based on profile 1.0 or 1.0.1 during provisioning are the likely exposure. Risk depends on physical proximity, provisioning workflow, and AuthValue randomness.
Exploitation context
The source bundle does not show KEV listing or active exploitation. Exploitation is proximity-based and conditional on successful brute force against an insufficiently random AuthValue within the provisioning timeout.
Researcher notes
Evidence is limited to specification-level exposure. Product impact, scoring, exploit maturity, and fixed versions are not provided in the bundle. Validation should focus on implementation behavior, AuthValue generation, and vendor-specific Bluetooth Mesh stack guidance.
Mitigation direction
- Inventory Bluetooth Mesh devices and provisioning workflows.
- Check device vendors and Bluetooth guidance for applicable updates.
- Use high-entropy random AuthValues for provisioning where configurable.
- Restrict provisioning to controlled physical locations and short windows.
- Monitor for unexpected or unauthorized mesh nodes.
Validation and detection
- Confirm whether deployed devices use Bluetooth Mesh Profile 1.0 or 1.0.1.
- Review provisioning configuration for AuthValue generation and entropy.
- Verify firmware or stack updates against vendor advisories.
- Audit mesh membership for unknown provisioned devices.
- Document compensating controls for provisioning environments.
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.
CVE-2020-26556 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- VU#799380CVE reference · third-party-advisory, x_refsource_CERT-VN
- https://www.bluetooth.com/learn-about-bluetooth/key-attributes/bluetooth-security/reporting-security/CVE reference · x_refsource_MISC
- https://kb.cert.org/vuls/id/799380CVE reference · x_refsource_MISC
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.