dbcve.org
Mesh ProfileApplication · Bluetooth

CVE-2020-26560

HIGH · 8.1 CVSS v3.1 Published 2021-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Bluetooth Mesh Provisioning in the Bluetooth Mesh profile 1.0 and 1.0.1 may permit a nearby device, reflecting the authentication evidence from a Provisioner, to complete authentication without possessing the AuthValue, and potentially acquire a NetKey and AppKey.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A reflection attack vulnerability in Bluetooth Mesh Provisioning (profiles 1.0 and 1.0.1) allows a nearby attacker to relay authentication evidence from a legitimate Provisioner back to itself, completing authentication without possessing the actual AuthValue. Successful exploitation grants the attacker network keys (NetKey) and application keys (AppKey), enabling full access to the Bluetooth Mesh network.

MitigationImplement anti-reflection/anti-relay protections in provisioning protocols, utilize Out-of-Band (OOB) authentication methods, and ensure provisioning links use link-layer encryption to prevent authentication reflection attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mesh ProfileApplication
Affected:= 1.0.0= 1.0.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Bluetooth Mesh Provisioning is in use
    Identify whether your system or device implements Bluetooth Mesh networking functionality, specifically the provisioning process that adds new nodes to a mesh network
    Affected if Bluetooth Mesh Provisioning is actively used or deployed in your environment
  2. Identify the Bluetooth Mesh Profile version
    Locate and inspect the version of the Bluetooth Mesh Profile implementation (stack, library, or firmware) used by your Provisioner device. Consult product documentation, firmware metadata, or system logs that report the mesh profile version.
    Affected if The implemented Bluetooth Mesh Profile version is exactly 1.0.0 or 1.0.1
  3. Determine if the device operates as a Provisioner
    Check whether your device or system is configured to perform the Provisioner role, which handles adding and authenticating new nodes to the mesh network. Review device roles, capabilities, or configuration settings related to provisioning.
    Affected if The device is capable of acting as a Provisioner in a Bluetooth Mesh network
  4. Verify provisioning link security configuration
    Inspect the provisioning protocol configuration to determine whether link-layer encryption is enforced during the provisioning procedure. Review security settings or protocol documentation for the provisioning link.
    Affected if Provisioning links lack link-layer encryption and rely solely on the standard authentication flow without anti-reflection protections

You are affected if your environment uses Bluetooth Mesh Provisioning with profile version 1.0.0 or 1.0.1 on a device operating as a Provisioner, and the provisioning protocol lacks anti-reflection protections or link-layer encryption.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-reflection/anti-relay protections in provisioning protocols, utilize Out-of-Band (OOB) authentication methods, and ensure provisioning links use link-layer encryption to prevent authentication reflection attacks.

Fix this in Mesh Profile Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-26560 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-26560 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data