Loading story…
Eppendorf and CISA disclosed a critical vulnerability in all versions of the BioFlo 320 bioreactor that could let a remote attacker with network access take full control of the system’s user interface and associated functions and data. The issue, tracked as CVE-2026-7251 and mapped to CWE-259, carries a CVSS 9.8 rating and stems from a VNC-based remote management component that uses a hard-coded password; CISA also warned that the VNC traffic is not encrypted, increasing risk where remote access is enabled.
The BioFlo 320 is used in laboratory and healthcare environments, raising concerns that unauthorized access could allow manipulation of sensitive biochemical processes. Eppendorf released Version 5.0 to disable the vulnerable remote control protocol and urged administrators to apply the update immediately, while also confirming the affected remote feature was disabled by default and could only be enabled manually at the physical workstation tower. CISA said BIO-ISAC reported the flaw and that it had no evidence of public exploitation at the time of publication; defenders were also advised to verify local role-based protections so only trusted supervisors can change configurations.
See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
Eppendorf released a software update, Version 5.0, that disables the vulnerable remote control protocol in the BioFlo 320. Researchers said the flaw, tracked as CVE-2026-7251, could allow unauthenticated administrative access via the VNC-based remote management component if the feature had been enabled.
On 2026-05-26, CISA published advisory ICSMA-26-146-01 for a critical vulnerability affecting all versions of the Eppendorf BioFlo 320 Bioreactor. The advisory said the VNC server uses a hard-coded password, enabling a remote attacker with network access to gain full control, and noted there were no reports of public exploitation at that time.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Siemens disclosed **CVE-2026-58115**, a critical authentication bypass in **SIMATIC IoT2050 Advanced** and **Advanced PG** devices running Industrial OS with **Node-RED** installed. The flaw affects the Node-RED HTTP interface, which lacks authentication and allows unauthenticated remote attackers to access programming functions, send crafted requests to the ` /flows ` API, and deploy malicious flows that execute arbitrary operating system commands with **root** privileges. The issue is tracked as **CWE-306** and carries a **CVSS 3.1 score of 10.0**. The vulnerability affects **all versions earlier than `V4.3.4.1`** when Node-RED is installed; devices without Node-RED are not impacted. Siemens released **`V4.3.4.1`** to fix the issue. Reporting indicates there was no public proof-of-concept or confirmed active exploitation at publication, but the exposure is significant because SIMATIC IoT2050 devices often connect corporate IT and OT networks, raising the risk of operational disruption and potential downstream effects on connected PLCs and industrial processes.
Aug 12, 2026
Threat actors are actively exploiting **CVE-2025-59528**, a **CVSS 10.0** remote code execution flaw in the open-source AI platform **Flowise**. The bug affects Flowise versions through **3.0.5** and stems from the `CustomMCP` node unsafely passing user-controlled input into JavaScript execution, allowing attackers with an API token to run arbitrary code with full **Node.js** runtime privileges. Researchers said the issue can be triggered remotely via a crafted HTTP `POST` request without user interaction, leading to operating system command execution, filesystem access, sensitive data theft, and full system compromise. Security researchers observed in-the-wild exploitation originating from a single **Starlink IP address**, while warning that roughly **12,000 to 15,000** internet-exposed Flowise instances sharply expand the attack surface for opportunistic attacks. Flowise disclosed the vulnerability in 2025, credited researcher **Kim SooHyun**, and patched the flaw in **version 3.0.6**. The incident marks the third Flowise vulnerability reported as exploited in the wild after **CVE-2025-8943** and **CVE-2025-26319**, increasing pressure on organizations to upgrade immediately and limit public exposure of Flowise APIs.
Jun 29, 2026
Flowise disclosed a critical remote code execution flaw, tracked as **`CVE-2026-56274`**, affecting versions before **`3.1.2`** in the Custom MCP Server feature. The vulnerability stems from multiple OS command injection paths in **`validateCommandFlags`** and **`validateArgsForLocalFileAccess`**, allowing attackers to configure a malicious MCP server and execute arbitrary commands on the Flowise host. The issue is rated **CVSS 9.9** and is remotely exploitable. Advisories describe three bypass techniques: an incomplete Docker argument blocklist that permits **`docker build`** with a remote URL, an **`npx`** blocklist bypass where **`--yes`** is allowed even though **`-y`** is blocked, and a Unix path validation weakness that lets paths beginning with **`//`** evade local file access checks for **`node`**. Exploitation requires any Flowise account role or API access with view and update permissions for chatflows. Organizations were urged to upgrade to **`Flowise 3.1.2`** or later, review MCP server configurations, and restrict chatflow management permissions.
Jun 29, 2026