CVE-2020-26559

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.

Published: 2021-05-24 Last update: 2025-11-04 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-26559 is rated Moderate Risk (62.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.27%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-26559

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-02-11 1.65% 1.27% -0.38%
2 2025-11-21 0.40% 1.65% +1.26%
3 2025-11-18 — 0.40% —

Full EPSS history (14 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-26559

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:A)
Attacker has to be nearby on the network—same office, same link, that vibe—not the whole wide internet.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
5.8 2.0 MEDIUM
AV:A/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:A)
Requires access to an adjacent network segment.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 6.5 6.4 [email protected]

Weakness enumeration for CVE-2020-26559

OS Trackers for CVE-2020-26559

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2020-26559
suse medium CVE-2020-26559 severity moderate: SUSE including 20 source package names (bluez, bluez-cups, …), 421 product×package rows across 71 product lines (SUSE CaaS Platform 4.0, SUSE Enterprise Storage 7, … (71 product lines)): Known Not Affected 421. https://www.suse.com/security/cve/CVE-2020-26559/
ubuntu medium CVE-2020-26559 medium priority: Ubuntu including 167 source packages (linux, linux-allwinner, …), 2145 status rows across 16 suites (bionic, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): DNE 1677, ignored 307, needs-triage 161. https://ubuntu.com/security/CVE-2020-26559

Affected software / configurations for CVE-2020-26559

Vendor Product Version Raw CPE
bluetooth mesh_profile 1.0.0 cpe:2.3:a:bluetooth:mesh_profile:1.0.0:*:*:*:*:*:*:*
bluetooth mesh_profile 1.0.1 cpe:2.3:a:bluetooth:mesh_profile:1.0.1:*:*:*:*:*:*:*

References for CVE-2020-26559

cvelogic Threat Intelligence