CVE-2024-48289: Cypress Bluetooth SDK · Classic Buffer Overflow
Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% 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:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Nov 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 26 Oct 2026.
What to do
AI-suggested
Organizations should immediately inventory devices and products using Cypress Bluetooth SDK v3.66 to identify exposure. Since no patches are currently available, mitigating controls include limiting physical and wireless access to BLE interfaces, such as disabling BLE when not in use or restricting BLE communication range. Network segmentation and monitoring for anomalous BLE traffic patterns, especially malformed LL_PAUSE_ENC_REQ packets, can help detect exploitation attempts. Vendors and developers should prioritize updating to patched SDK versions once released by Cypress. For critical environments, consider deploying BLE intrusion detection systems or employing fallback communication channels to maintain availability during attacks. Additionally, applying strict input validation and robust error handling in BLE stack implementations can reduce the risk of similar vulnerabilities.
Description
An issue in the Bluetooth Low Energy implementation of Cypress Bluetooth SDK v3.66 allows attackers to cause a Denial of Service (DoS) via supplying a crafted LL_PAUSE_ENC_REQ packet.