CVE-2026-2756
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMissing authentication in the BLE interface of OmniPEMF NeoRhythm devices (up to 20260308) allows unauthenticated attackers within the local network to interact with the BLE component. The attack requires high complexity and is difficult to exploit, but requires no credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OmniPEMF NeoRhythm devices on the networkScan the local network for devices advertising the service name 'NeoRhythm' or vendor UUID 0xFE9F (BLE GATT service). Use tools like 'hcitool lescan' or BLE scanner apps to enumerate BLE peripherals.Affected if A device responding to BLE queries with NeoRhythm branding or matching UUID is found on the network.
-
Verify BLE interface is enabled and accessibleAttempt a BLE connection to the device using tools like 'gatttool' or 'bleah' with the device MAC address. Test if read/write operations are possible without pairing or authentication.Affected if BLE connection succeeds and GATT characteristics are readable or writable without requiring PIN, passkey, or bond creation.
-
Determine firmware versionConnect via BLE and read the device information service (GATT 0x180A) to obtain the firmware version string. Alternatively, check the device management interface for a version field showing '20260308' or earlier.Affected if Firmware version is '20260308' or earlier, or the version field cannot be retrieved (indicating outdated firmware).
-
Assess network exposureReview network segmentation and VLAN assignments. Determine if the device resides on the same broadcast domain as untrusted users or guest networks. Check firewall rules or ACLs controlling access to the device IP address.Affected if The device is reachable from network segments containing untrusted or unmanaged devices without intervening access controls.
A defender is affected if a NeoRhythm device with accessible BLE interface and firmware version 20260308 or earlier is present on a network segment accessible to untrusted actors.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataIsolate NeoRhythm devices on a dedicated network segment with strict ACLs; monitor BLE traffic for unauthorized access attempts; contact vendor through alternative channels or evaluate device replacement given lack of vendor response.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2756 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2756 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data