# CVE-2026-50034: Apollo Pharmacy Blood Glucose Monitoring System APG-01 BT Cleartext Transmission of Sensitive Information

> Attackers within Bluetooth range can intercept cleartext traffic to steal sensitive glucose measurement data from the device.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 18 Jun 2026
- **Updated:** 22 Jun 2026
- **Also known as:** GHSA-cmv8-9pgg-5rx4

## What is CVE-2026-50034?

CVE-2026-50034 is a high-severity vulnerability in Apollo Pharmacy Blood Glucose Monitoring System (Model No. APG-01 BT), published on 18 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An attacker within BLE communication range can passively intercept 
wireless traffic and obtain sensitive health-related information, 
including glucose measurement values.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

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


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

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

## Is CVE-2026-50034 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50034 is a high-severity vulnerability in Apollo Pharmacy Blood Glucose Monitoring System (Model No. APG-01 BT), published on 18 Jun 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-50034 in the wild and no public exploit code.

Affected product: Apollo Pharmacy Blood Glucose Monitoring System (Model No. APG-01 BT). 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-50034/ (Markdown: https://insights.sbomify.com/CVE-2026-50034/index.md)
```

## Sources

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

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