CVE-2026-97402 · Infrastructure
NO FIX YET
Eclipse Kura's iBeacon and Eddystone decoders misparse the length field of BLE advertisements, so a two-byte broadcast sends the beacon scanner into an infinite loop. An attacker within Bluetooth range can pin a CPU core and stop beacon ingestion until the gateway restarts.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only gateways running Eclipse Kura 3.1.0 to 5.6.2 with the iBeacon or Eddystone scanner component installed and enabled are exposed. The attack needs no account, but the attacker must be within BLE radio range of the gateway. Gateways without that component, or running a version outside the range, can skip it.
Not affected if default-config, no-ble-scanner
Who cares bluetooth-ble, eclipse-kura, iot-gateway
3.1.0 through 5.6.2.No fix yet, per the sources.
In Eclipse Kura versions 3.1.0 to 5.6.2, the iBeacon and Eddystone advertisement decoders wrongly parse the AD-structure length field of an over-the-air BLE advertising payload. Any unauthenticated attacker within BLE radio range can broadcast a two-byte advertising payload that drives the Kura beacon-scanner thread into a tight infinite loop, pinning a CPU core and permanently halting beacon ingestion until the gateway is restarted. To trigger the attack, the iBeacon/Eddystone scanner component should be installed and active. By default the components are not installed or enabled.
This page as .md · .json · CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.