Severity:

CRITICAL RISK

(9.8)

Hard-Coded Credentials in Eppendorf BioFlo 320 Control

CVE-2026-7251

Awaiting Analysis

Vulnerability type

Category:

Hard-Coded Credentials

CWE:

CWE-259

Impact:

Remote Takeover of Device Control Interface

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Eppendorf BioFlo 320 systems expose a VNC server protected by a hard-coded password, allowing anyone who knows this password and the device's network address to log in remotely.

With remote access enabled, an attacker can gain full control of the device's user interface over an unencrypted VNC connection, potentially manipulating all available control panel features.

Affected context

This vulnerability arises in BioFlo 320 deployments where:

  • The built-in VNC-based remote access feature is enabled
  • Devices are reachable over IP networks (LAN, laboratory network, or VPN)
  • Operators rely on the default or vendor-provided VNC configuration

In such environments, the presence of a non-changeable, hard-coded password and unencrypted VNC traffic means that anyone who knows or discovers the password and can reach the device over the network may control the user interface.

Exploit preconditions

  • Attack surface: Network-accessible VNC service exposed by the BioFlo 320
  • Required access: Network connectivity to the device (e.g., same subnet, routed network, or VPN) and knowledge of the hard-coded password
  • Trigger point: Initiating a VNC connection to the device's IP/port and supplying the hard-coded credentials
  • Why exploitation is possible: The VNC server uses a vendor-defined password that cannot be individually managed per device, and the protocol traffic is transmitted without encryption, providing no additional confidentiality or authentication layering.

Why this happens

The underlying issue maps to CWE-259: Use of Hard-coded Password, where a fixed credential is embedded in the system or its configuration and reused across deployments.

Instead of deriving authentication secrets from a per-device configuration or allowing operators to define unique credentials, the VNC service relies on a static password that is effectively shared by all affected devices.

Because this credential is not bound to any particular user identity, cannot be rotated easily, and is identical across installations, it undermines the authentication boundary and enables broad, unauthorized access when combined with network reachability.

Potential impact

  • Remote attackers could gain full control of the BioFlo 320 user interface.
  • Attackers could start, stop, or alter running processes and operational parameters.
  • Device configuration and calibrations could be modified or disrupted.
  • Operational data displayed through the control panel could be manipulated or obscured.
  • Unencrypted VNC sessions could be intercepted, allowing credential reuse and session hijacking.

General mitigation guidance

Effective mitigation patterns focus on reducing exposure of fixed credentials and limiting network reachability of sensitive interfaces:

  • Place devices behind restrictive network boundaries, limiting VNC access to tightly controlled segments or jump hosts.
  • Introduce compensating access controls such as VPNs, bastion hosts, or application-layer gateways to add separate authentication and encryption layers in front of VNC.
  • Use network-level controls (firewalls, ACLs, segmentation) to restrict which hosts can initiate VNC connections.
  • Prefer remote access mechanisms that support per-user, changeable credentials and strong encryption instead of relying on fixed passwords.
  • Apply least-privilege principles by ensuring only necessary personnel and systems can reach the control interface.

How teams detect issues like this

Organizations can approach detection by combining network, configuration, and process-level reviews:

  • Network scanning tools can identify exposed VNC services on BioFlo 320 devices and verify their accessibility from various network zones.
  • Configuration assessments and asset inventories can flag devices that rely on static or vendor-defined credentials for remote access.
  • Security monitoring can track VNC connection attempts, unusual access patterns, and cross-network connections into laboratory segments.
  • Policy-based controls (e.g., NAC rules, firewall policies) can enforce that sensitive control systems are not directly reachable from general-purpose networks.
  • Regular security reviews and audits of operational technology (OT) environments can help discover and document remote access paths relying on hard-coded passwords.

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsma-26-146-01.json
cisa.govcisa.gov/news-events/ics-medical-advisories/icsma-26-146-01
eppendorf.comeppendorf.com/software-downloads

Frequently asked

questions

It can be, if the BioFlo 320's VNC interface is reachable from the internet or untrusted networks. In many environments, exposure may be limited to internal or laboratory networks, but any reachable attack path combined with the hard-coded password enables remote exploitation.

An attacker must be able to reach the device over the network (for example, being on the same LAN, connected via VPN, or passing through misconfigured firewalls) and must know or obtain the hard-coded VNC password. No additional per-user credentials or local access are required once these conditions are met.

The most robust pattern is to eliminate direct reliance on static, non-changeable passwords for remote access and to insert strong, separate authentication and encryption layers in front of device interfaces. This typically involves placing devices behind secured gateways, enforcing unique credentials, and isolating OT systems on protected network segments.

Future deployments should favor designs where each device uses configurable, per-user credentials and modern encrypted remote access protocols. Security architecture practices such as network segmentation, strict exposure management, and regular review of remote access methods help ensure that no control interface depends solely on hard-coded or vendor-shared passwords.

Find out what's already
exploitable in your codebase.