# CVE-2026-5768: Fourth Frontier Frontier X Mobile Application, Frontier X2 Missing Authentication for Critical Function

> Attackers within Bluetooth range can access critical device functions and inject fake health data due to missing authentication in the Frontier X2 wearable and mobile app.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 29 May 2026
- **Also known as:** GHSA-frhh-w545-jjh2

## What is CVE-2026-5768?

CVE-2026-5768 is a high-severity missing authorization vulnerability in Fourth Frontier Frontier X Android application, published on 29 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Frontier X2 device allows unauthenticated BLE read/write access to critical GATT characteristics without enforcing pairing authentication or authorization. This allows attackers within BLE range to perform unauthorized control of device functions, including starting/stopping activities, triggering vibrations, causing denial-of-service conditions, and fuzzing characteristic values to induce unexpected behavior. Additionally, the Frontier X mobile application lacks proper BLE device authentication, allowing attackers to impersonate a legitimate Frontier X2 device and connect to the application. By cloning BLE advertisements and exposing expected GATT characteristics, attackers can manipulate activity states and inject fabricated health telemetry such as breathing rate, heart rate, strain, and other health-related data into the mobile application.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


## How do I fix CVE-2026-5768?

No fix has been published for CVE-2026-5768 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5768 being exploited?

There is no known exploitation of CVE-2026-5768 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5768 and fix it if it is affected.

What it is: CVE-2026-5768 is a high-severity missing authorization vulnerability in Fourth Frontier Frontier X Android application, published on 29 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5768 in the wild and no public exploit code.

Affected product: Fourth Frontier Frontier X Android application. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5768/ (Markdown: https://insights.sbomify.com/CVE-2026-5768/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5768
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5768
- OSV: https://osv.dev/vulnerability/CVE-2026-5768

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5768/
Summaries are generated and may contain mistakes; the official description above is the record.