LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26557: Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (without possessio...

Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (without possession of the AuthValue used in the provisioning protocol) to determine the AuthValue via a brute-force attack (unless the AuthValue is sufficiently random and changed each time).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-26557 concerns Bluetooth Mesh provisioning. A nearby device may be able to learn the provisioning AuthValue by brute force if that value is weak, reused, or not changed. This matters most for organizations deploying Bluetooth Mesh devices in physical spaces where outsiders or untrusted devices can get close during provisioning.

Executive priority

Treat this as a targeted exposure review for Bluetooth Mesh deployments, not a broad enterprise emergency. Prioritize sites with wireless mesh devices in public or semi-public spaces and weak provisioning practices.

Technical view

Bluetooth Mesh profile 1.0 and 1.0.1 provisioning may allow an adjacent attacker without the AuthValue to determine it through brute force unless the AuthValue is sufficiently random and changed for each provisioning session. The source bundle does not identify specific vendors, products, CVSS, CWE, or a named patch.

Likely exposure

Exposure is likely limited to environments using Bluetooth Mesh 1.0 or 1.0.1 provisioning, especially where AuthValues are static, predictable, low entropy, or reused. Practical risk requires nearby Bluetooth radio proximity and depends on device implementation and provisioning workflow.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The described attack requires proximity to Bluetooth Mesh provisioning activity and weaknesses in AuthValue generation or reuse. Evidence is incomplete for real-world exploitation prevalence.

Researcher notes

This appears to be a Bluetooth Mesh profile-level issue rather than a product-specific advisory in the supplied bundle. Product impact, scoring, and fixes are not enumerated. Research should focus on implementation behavior, AuthValue entropy, reuse, and vendor-specific guidance.

Mitigation direction

  • Inventory Bluetooth Mesh devices and provisioning tools in use.
  • Check vendor and Bluetooth guidance for security updates or advisories.
  • Use sufficiently random AuthValues for every provisioning session.
  • Do not reuse static, predictable, or shared provisioning AuthValues.
  • Restrict provisioning to controlled physical locations and trusted operators.

Validation and detection

  • Confirm whether deployed devices use Bluetooth Mesh 1.0 or 1.0.1.
  • Ask vendors whether their implementations are affected by CVE-2020-26557.
  • Review provisioning procedures for AuthValue randomness and one-time use.
  • Check whether firmware or provisioning tools have available security updates.
  • Validate that provisioning occurs only in controlled, monitored areas.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2020-26557 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.