LiveActive security incident?Get immediate response
CVE Record

CVE-2020-26555: Bluetooth legacy BR/EDR PIN code pairing in Bluetooth Core Specification 1.0B through 5.2 may permit an una...

Bluetooth legacy BR/EDR PIN code pairing in Bluetooth Core Specification 1.0B through 5.2 may permit an unauthenticated nearby device to spoof the BD_ADDR of the peer device to complete pairing without knowledge of the PIN.

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

Security readout for executives and security teams

Plain-English summary

This issue affects older Bluetooth BR/EDR PIN-code pairing behavior. A nearby unauthenticated device may impersonate another Bluetooth device address and finish pairing without knowing the PIN. The business risk is localized: it depends on Bluetooth use, legacy pairing support, and vendor implementation details.

Executive priority

Treat this as a targeted exposure-review item, not a broad emergency from the supplied evidence. Prioritize environments with managed endpoints, industrial devices, medical devices, or sensitive facilities where nearby Bluetooth pairing abuse could matter.

Technical view

Bluetooth Core Specification 1.0B through 5.2 legacy BR/EDR PIN pairing may allow BD_ADDR spoofing during pairing, letting an unauthenticated nearby device complete pairing without PIN knowledge. The source bundle provides no CVSS, CWE, full affected product matrix, exploit chain, or universal fix.

Likely exposure

Exposure is most likely in Bluetooth-enabled systems that support legacy BR/EDR PIN-code pairing. It requires nearby radio access and relevant pairing conditions. Product impact is implementation-specific; the bundle references CERT, Bluetooth, Fedora, and Intel sources but does not provide a complete affected-vendor list.

Exploitation context

The source bundle does not show active exploitation, and KEV is false. Evidence supports a proximity-based Bluetooth pairing weakness, not Internet-routable exploitation. Real-world risk depends on whether devices still permit legacy BR/EDR PIN pairing and whether vendor updates exist.

Researcher notes

The key evidence is protocol-level: legacy BR/EDR PIN pairing can be completed through peer BD_ADDR spoofing without PIN knowledge. Missing CVSS, CWE, exploit status, and complete affected products limit confidence. Validation should focus on implementation exposure and vendor advisories.

Mitigation direction

  • Check Bluetooth, OS, chipset, and distribution vendor advisories for applicable updates.
  • Prioritize assets that use Bluetooth BR/EDR pairing in sensitive environments.
  • Disable legacy Bluetooth PIN pairing where vendor guidance and operations allow.
  • Restrict Bluetooth pairing on managed devices where it is not business-required.
  • Track Intel, Fedora, CERT, and Bluetooth SIG guidance for product-specific direction.

Validation and detection

  • Inventory devices and software stacks that support Bluetooth BR/EDR pairing.
  • Confirm whether legacy PIN-code pairing is enabled or permitted.
  • Check vendor advisory applicability for chipsets, operating systems, and packages.
  • Verify installed Bluetooth stack versions against vendor-fixed releases, where provided.
  • Review device management policy for unnecessary Bluetooth pairing exposure.
Prepared
Confidence
medium
Sources
6

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-26555 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
6Source 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.