LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-7251 is a critical issue in Eppendorf BioFlo 320 systems. A built-in VNC password can let anyone who can reach the device over the network take full control of its user interface if remote access is enabled. The VNC session is also unencrypted, increasing confidentiality risk.

Executive priority

Treat this as urgent for labs using BioFlo 320. The issue can allow remote control of equipment without credentials, potentially affecting experiments, production workflows, and data integrity. Prioritize exposure reduction immediately, especially network isolation and remote-access review.

Technical view

All Eppendorf BioFlo 320 versions are reported affected. The issue is CWE-259: use of a hard-coded password in the VNC server. Network exploitation requires no authentication, no user interaction, and low attack complexity. Successful access gives full control panel functionality. CVSS is 9.8, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is highest where BioFlo 320 systems have remote access enabled and are reachable from enterprise, lab, vendor, or internet-connected networks. The sources do not state whether remote access is enabled by default. Organizations should treat any reachable VNC service on these devices as high risk.

Exploitation context

CISA and CVE sources describe remote unauthenticated access if the attacker knows the device network address and the hard-coded password. The provided sources do not report active exploitation, and the CVE is not listed as KEV in the supplied data.

Researcher notes

The public description names hard-coded VNC credentials and unencrypted VNC traffic but does not provide patch status in the supplied bundle. Avoid assuming a firmware fix exists. Focus validation on asset discovery, reachability, remote-access status, and whether vendor guidance has changed.

Mitigation direction

  • Identify all BioFlo 320 systems and owners.
  • Restrict network access to the device and VNC service.
  • Disable remote access where it is not required.
  • Place devices behind controlled lab or OT network segmentation.
  • Check Eppendorf software downloads and CISA advisory for vendor guidance.
  • Monitor for unexpected remote sessions or configuration changes.

Validation and detection

  • Confirm whether each BioFlo 320 has remote access enabled.
  • Verify the device is not reachable from untrusted networks.
  • Review firewall rules allowing access to the device.
  • Check vendor and CISA sources for updates or advisories.
  • Document compensating controls for systems awaiting vendor remediation.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-259: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-7251 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9icscert
9.3CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——icscert

Vulnerability scoring details

Base CVSS 4.0 score

9.3Critical
CVSS 4.0 vector shape for CVE-2026-7251Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
EppendorfBioFlo 320Allunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-259 · source CWE mapping

Use of Hard-coded Password

Use of Hard-coded Password represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.