LiveActive security incident?Get immediate response
CVE Record

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

Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device (participating in the provisioning protocol) to identify the AuthValue used given the Provisioner’s public key, and the confirmation number and nonce provided by the provisioning device. This could permit a device without the AuthValue to complete provisioning without brute-forcing the AuthValue.

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-26559 affects Bluetooth Mesh provisioning in profile versions 1.0 and 1.0.1. A nearby device participating in provisioning may determine the provisioning AuthValue and join without knowing it beforehand. This is most relevant to organizations using Bluetooth Mesh for building, industrial, IoT, or physical-security systems.

Executive priority

Treat this as a targeted IoT and physical-proximity risk, not an internet-scale emergency. Prioritize asset discovery and vendor confirmation for Bluetooth Mesh deployments that support safety, access, facilities, or operational processes.

Technical view

During Bluetooth Mesh provisioning, a nearby participating device may identify the AuthValue from the Provisioner public key plus the confirmation number and nonce supplied by the provisioning device. The source bundle does not provide CVSS, CWE, product CPEs, or vendor-specific fixed versions.

Likely exposure

Exposure is limited to environments using Bluetooth Mesh profile 1.0 or 1.0.1, especially where provisioning occurs in reachable physical proximity. The bundle does not identify specific vendors, products, or firmware versions.

Exploitation context

The CVE requires a nearby device involved in the provisioning protocol. There is no KEV listing in the bundle and no cited evidence of active exploitation. The practical risk depends on device fleet, provisioning controls, and vendor implementation details.

Researcher notes

The strongest evidence is the CVE description and CERT/BT references. Missing data limits precision: no CVSS, CWE, named affected products, exploit evidence, or patch matrix appears in the provided bundle.

Mitigation direction

  • Check Bluetooth SIG and device vendor guidance for corrected mesh stack or firmware updates.
  • Inventory devices using Bluetooth Mesh profile 1.0 or 1.0.1.
  • Limit provisioning windows to controlled maintenance periods.
  • Restrict physical access near devices during provisioning.
  • Audit mesh membership for unexpected provisioned nodes.

Validation and detection

  • Confirm whether deployed devices support Bluetooth Mesh profile 1.0 or 1.0.1.
  • Map provisioning processes, locations, operators, and maintenance windows.
  • Review vendor advisories for affected firmware and update availability.
  • Check mesh node inventories for unauthorized or unexplained additions.
  • Document compensating controls where vendor fixes are unavailable.
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-26559 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.