CVE-2024-44124VulnerabilityPublished 16 Sep 2024Updated 2 Apr 2026

CVE-2024-44124: Apple iOS and iPadOS · A malicious Bluetooth input device may bypass pairing

Affects Apple iOS and iPadOSSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Sep 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Apple iOS and iPadOS	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2024-44124, organizations and users should promptly update all iOS and iPadOS devices to version 18 or later, where the vulnerability is fixed. Beyond patching, organizations should enforce strict Bluetooth usage policies, including disabling Bluetooth when not in use and restricting device discoverability. Implement device management solutions to monitor and control Bluetooth connections and detect unauthorized devices. Educate users about the risks of connecting to unknown Bluetooth devices and encourage vigilance in public or shared environments. For high-security environments, consider disabling Bluetooth input device support entirely or using additional endpoint security controls to detect anomalous input behavior. Regularly audit device configurations and Bluetooth logs for suspicious activity. Finally, coordinate with Apple support and security advisories to stay informed about any emerging threats or additional patches related to Bluetooth vulnerabilities.

Description

This issue was addressed through improved state management. This issue is fixed in iOS 18 and iPadOS 18. A malicious Bluetooth input device may bypass pairing.

Impact

The primary impact of CVE-2024-44124 is on the integrity of affected iOS and iPadOS devices. An attacker with a malicious Bluetooth input device can bypass pairing and inject unauthorized input commands, potentially executing arbitrary actions on the device. This could lead to unauthorized configuration changes, data manipulation, or execution of commands without user consent. Although confidentiality and availability are not directly affected, the integrity compromise can facilitate further attacks such as social engineering, phishing, or unauthorized access to sensitive applications. Organizations relying heavily on Apple mobile devices, especially in sensitive environments, face risks of device manipulation and potential data compromise. The attack requires physical proximity, limiting remote exploitation but still posing a significant threat in public or shared spaces. The lack of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits following disclosure. Failure to update devices leaves them vulnerable to unauthorized control via Bluetooth input spoofing.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Apr 2026, 23:42 UTC

Technical details

References

Community reviews

Related threats