CVE-2026-52866
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 · uneditedAn attacker within BLE communication range can monopolize the device's only available BLE connection slot, preventing legitimate users or applications from establishing a connection.
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 · moderate confidenceAn attacker within BLE communication range can monopolize the device's only available BLE connection slot by establishing and holding a connection, effectively preventing any legitimate users or applications from connecting to the device - a denial of service via connection slot exhaustion.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm BLE is enabledCheck the device's Bluetooth settings or configuration to verify BLE functionality is active. This may be via a settings UI, config file, or system command (e.g., hciconfig on Linux, or checking service status).Affected if BLE is enabled and the device has only a single connection slot available
-
Identify the number of available BLE connection slotsConsult the device documentation, firmware specifications, or BLE stack configuration to determine how many simultaneous BLE connections the device supports. On Linux, this may be verifiable via BLE stack tools or kernel parameters.Affected if The device supports only one simultaneous BLE connection (single connection slot)
-
Check for BLE connection timeout configurationInspect the BLE stack or application configuration for any connection timeout settings. Look for parameters controlling how long an idle or authenticated connection persists before being automatically terminated.Affected if No connection timeout is configured, or timeouts are set to an excessively long duration that allows a connection to be held indefinitely
-
Verify BLE authentication requirementsExamine the BLE security configuration to determine if authentication (PIN, passkey, OOB, or LE Secure Connections) is required before the connection is fully established and functional.Affected if No authentication is required before granting BLE access, or connections are granted immediately upon pairing without additional verification
The device is affected if it supports only a single BLE connection slot AND lacks both connection timeouts AND authentication requirements, allowing an attacker to hold the sole slot indefinitely.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement connection timeouts, require authentication before granting connections, and enable multiple simultaneous connection slots to prevent a single attacker from permanently blocking legitimate access.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-52866 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-52866 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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