Unauthenticated controller takeover via hard-coded VNC password
Published May 26, 2026 · Updated May 26, 2026
Hard-coded credentials in all versions of Eppendorf BioFlo 320 allow remote attackers to control the interface through enabled VNC. The embedded VNC server accepts a shared hard-coded password for every unit and carries the session over an unencrypted connection. VNC is disabled by default and can be enabled only locally at the tower; exposure requires enabled VNC and knowledge of the unit's network address.
Summary
What happened
Hard-coded credentials in all versions of Eppendorf BioFlo 320 allow remote attackers to control the interface through enabled VNC. The embedded VNC server accepts a shared hard-coded password for every unit and carries the session over an unencrypted connection. VNC is disabled by default and can be enabled only locally at the tower; exposure requires enabled VNC and knowledge of the unit's network address.
The record
- CVE
- CVE-2026-7251
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- Eppendorf
- Product
- BioFlo 320
- Classifications
- CWE-259, T0886, T0859
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo