# CVE-2026-7251: Eppendorf BioFlo 320 Use of hard-coded password

> Remote attackers can gain full control of the Eppendorf BioFlo 320 interface using a hard-coded VNC password when remote access is enabled.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-v6xg-wr2p-xrj3

## What is CVE-2026-7251?

CVE-2026-7251 is a critical vulnerability in Eppendorf BioFlo 320, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Eppendorf BioFlo 320 is vulnerable due to VNC server using a hard-coded password. If a remote attacker knows the network address of any BioFlo 320 model with remote access enabled, they can gain full control of the user interface by using this password. Once connected, the attacker would have full access to all control panel features for the BioFlo 320. VNC traffic is not encrypted.

Weakness: CWE-259 (Use of Hard-coded Password)

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


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

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

## Is CVE-2026-7251 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7251 is a critical vulnerability in Eppendorf BioFlo 320, published on 26 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7251 in the wild and no public exploit code.

Affected product: Eppendorf BioFlo 320. 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-7251/ (Markdown: https://insights.sbomify.com/CVE-2026-7251/index.md)
```

## Sources

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

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