# CVE-2026-2756: OmniPEMF NeoRhythm BLE missing authentication

> Attackers within the local network can bypass authentication on the OmniPEMF NeoRhythm BLE interface due to missing security controls.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **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:** 21 Mar 2026
- **Updated:** 16 Sep 2026
- **Also known as:** GHSA-vm64-7vcf-58w4

## What is CVE-2026-2756?

CVE-2026-2756 is a low-severity authentication bypass vulnerability in OmniPEMF NeoRhythm, published on 21 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security vulnerability has been detected in OmniPEMF NeoRhythm up to 20260308. This affects an unknown function of the component BLE Interface. Such manipulation leads to missing authentication. The attack can only be initiated within the local network. This attack is characterized by high complexity. The exploitability is reported as difficult. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

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

## Is CVE-2026-2756 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2756 is a low-severity authentication bypass vulnerability in OmniPEMF NeoRhythm, published on 21 Mar 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-2756 in the wild and no public exploit code.

Affected product: OmniPEMF NeoRhythm. 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-2756/ (Markdown: https://insights.sbomify.com/CVE-2026-2756/index.md)
```

## Sources

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

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