Headphone access via Bluetooth source spoofing
Published Jun 26, 2024 · Updated Apr 2, 2026
Authentication bypass in Apple AirPods firmware allows physically proximate attackers to access headphones by spoofing a paired device. The Bluetooth reconnection state accepts a spoofed source as the intended previously paired device; Apple has not disclosed the erroneous state transition. Exploitation requires Bluetooth proximity while the headphones seek a connection to a previously paired device, and the documented consequence is access to the headphones.
Summary
What happened
Authentication bypass in Apple AirPods firmware allows physically proximate attackers to access headphones by spoofing a paired device. The Bluetooth reconnection state accepts a spoofed source as the intended previously paired device; Apple has not disclosed the erroneous state transition. Exploitation requires Bluetooth proximity while the headphones seek a connection to a previously paired device, and the documented consequence is access to the headphones.
The record
- CVE
- CVE-2024-27867
- Published
- Jun 26, 2024
- Updated
- Apr 2, 2026
- Vendor
- Apple
- Product
- AirPods
- Classifications
- CWE-287, T1036
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 26, 2024CVE publishedPublication date reported by the CVE source.
- Apr 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <unknown
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo