CVE-2023-45866

Bluetooth HID Hosts in BlueZ may permit an unauthenticated Peripheral role HID Device to initiate and establish an encrypted connection, and accept HID keyboard reports, potentially permitting injection of HID messages when no user interaction has occurred in the Central role to authorize such access. An example affected package is bluez 5.64-0ubuntu1 in Ubuntu 22.04LTS. NOTE: in some cases, a CVE-2020-0556 mitigation would have already addressed this Bluetooth HID Hosts issue.

CVSS: 6.3Medium
Exploited in the wild: Not knownUnvetted proof-of-concept code on GitHub; not in CISA KEV
EPSS: 7.9%chance of exploitation in the next 30 daystop 6% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 8 Dec 2023analysed here 12 Nov 2026

Summary

Triage

Attack surface: Server-side
Exploitable: At runtime
Attack vector: adjacent network
Weakness: CWE-287 Improper Authentication
Can a WAF block it?: No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

google:android
canonical:ubuntu_linux
apple:iphone_os
apple:macos
fedoraproject:fedora
apple:ipados
debian:debian_linux

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. Authentication bypass is a flaw in the application's logic. The attack requests look like normal traffic, so a WAF has nothing to match on.

Also consider: patch · add auth middleware

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog: Not listed as of our last sync.
Public exploit code: Unvetted proof-of-concept code on GitHub: 12 GitHub proofs of concept

GitHub proofs of concept

pentestfunctions/BlueDucky1,905 stars
Eason-zz/BluetoothDucky16 stars
Danyw24/blueXploit16 stars
AvishekDhakal/CVE-2023-45866_EXPLOITS3 stars

and 8 more repositories

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

8 Dec 2023Published
16 Jan 2024First proof-of-concept repository on GitHub (unvetted)39 days later
4 Nov 2025CVE record last updated659 days (about 2 years) later
12 Nov 2026Analysed by vulneraibility.com373 days (about 1 year) later

CVSS vector

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

Metric	Value	What it means
Attack vector	AdjacentSame subnet or link layer.	Same subnet or link layer.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	NoneNo victim action needed.	No victim action needed.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	LowPartial data disclosure.	Partial data disclosure.
Integrity	LowLimited modification possible.	Limited modification possible.
Availability	LowPartial degradation possible.	Partial degradation possible.

Common questions

Is CVE-2023-45866 being exploited?

Not confirmed. CVE-2023-45866 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 7.9% probability of exploitation in the next 30 days.

How severe is CVE-2023-45866?

CVE-2023-45866 is rated Medium with a CVSS score of 6.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-45866?

Yes. A fix has been recorded for CVE-2023-45866. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2023-45866 affect?

CVE-2023-45866 affects google:android, canonical:ubuntu_linux, apple:iphone_os, apple:macos, and 3 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVD CVE.org CVE Details Source

15 references in the CVE record, grouped by the tags the record gives them.

Advisories (4)

lists.fedoraproject.org /archives/list/package-announce%40lists.fedoraproject.org/message/D2N2P5LMP3V7IJ
lists.fedoraproject.org /archives/list/package-announce%40lists.fedoraproject.org/message/77YQQS5FXPYE6W
debian.org /security/2023/dsa-5584
security.gentoo.org /glsa/202401-03

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
FIRST EPSS: exploit probability and percentile
PoC-in-GitHub: GitHub repositories that claim a proof of concept

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.