Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-27867: When your headphones are seeking a connection request to one of your previously paired devices, an attacker in Bluetooth range might be able to spoof the intended source device and gain access to your headphones in Apple AirPods

0
Low
VulnerabilityCVE-2024-27867cvecve-2024-27867
Published: Wed Jun 26 2024 (06/26/2024, 03:12:26 UTC)
Source: CVE Database V5
Vendor/Project: Apple
Product: AirPods

Description

An authentication issue was addressed with improved state management. This issue is fixed in AirPods Firmware Update 6A326, AirPods Firmware Update 6F8, and Beats Firmware Update 6F8. When your headphones are seeking a connection request to one of your previously paired devices, an attacker in Bluetooth range might be able to spoof the intended source device and gain access to your headphones.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/02/2026, 23:15:22 UTC

Technical Analysis

CVE-2024-27867 is a Bluetooth authentication vulnerability identified in Apple AirPods and Beats headphones. The root cause is an authentication issue related to state management when the headphones seek to reconnect to a previously paired device. During this reconnection phase, an attacker within Bluetooth range can spoof the intended source device's identity, potentially gaining unauthorized access to the headphones. This could allow the attacker to interfere with the device's operation, such as disrupting audio or causing denial of service, though no direct confidentiality or integrity compromise is indicated. The vulnerability requires the attacker to be physically near the target device and for the headphones to be in the process of reconnecting, which involves user interaction or device activity. No privileges or prior authentication are required for exploitation. Apple has released firmware updates (6A326 for AirPods and 6F8 for Beats) that improve state management and authentication checks to fix this issue. The CVSS v3.1 base score is 3.3, reflecting low severity due to limited impact and exploitation complexity. There are no reports of active exploitation in the wild. This vulnerability highlights the importance of secure Bluetooth reconnection protocols and robust device authentication to prevent unauthorized access in wireless peripherals.

Potential Impact

The impact of CVE-2024-27867 is primarily limited to availability disruptions of Apple AirPods and Beats headphones during reconnection attempts. An attacker who successfully spoofs the source device could potentially interfere with the headphone's connection process, causing denial of service or unexpected behavior. However, the vulnerability does not allow access to sensitive data, nor does it enable modification or injection of audio streams, so confidentiality and integrity remain intact. For organizations, the risk is mostly to user experience and device reliability rather than critical security breaches. Nonetheless, in environments where AirPods are used for sensitive communications or in conjunction with secure systems, any disruption could have operational consequences. The requirement for physical proximity and user interaction limits the scope of exploitation, reducing the overall threat level. Still, widespread use of these devices globally means a large population could be affected if the vulnerability is exploited. Prompt firmware updates mitigate these risks effectively.

Mitigation Recommendations

To mitigate CVE-2024-27867, users and organizations should immediately update affected Apple AirPods and Beats headphones to the latest firmware versions (AirPods Firmware Update 6A326 and Beats Firmware Update 6F8). Firmware updates address the authentication and state management flaws that enable the spoofing attack. Additionally, users should be cautious when connecting headphones in public or untrusted environments where attackers could be nearby. Disabling Bluetooth when not in use reduces exposure to such attacks. For enterprise environments, enforcing policies that require device firmware to be up to date before allowing use on corporate networks can help. Monitoring Bluetooth device connections and employing Bluetooth security tools that detect anomalous pairing or connection attempts may provide additional protection. Finally, educating users about the risks of connecting to unknown or suspicious Bluetooth devices can reduce the likelihood of exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
apple
Date Reserved
2024-02-26T15:32:28.541Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69ceb827e6bfc5ba1df6e8e2

Added to database: 4/2/2026, 6:40:39 PM

Last enriched: 4/2/2026, 11:15:22 PM

Last updated: 4/3/2026, 5:56:16 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses