UNM cyberattack disrupts care; Palo Alto firewalls exploited
A New Mexico health system resumed operations after diverting ambulances. Palo Alto Networks now reports attacks on exposed firewall management interfaces, and a federal rule changes documentation requirements for certified decision-support software.
November 2, 2026 · Reporting week: October 26–November 1. Sources and status checked November 2 through 13:50 UTC. Later updates should be checked before publication.
CISO Quick Read
- UNM Health resumed care after an October 26 cyber incident. Ambulances were diverted for two hours and outpatient appointments and surgeries were suspended for the rest of the day. UNM said on October 28 that clinical operations were fully functional. UNM said the incident was under criminal investigation. What UNM reported.
- Palo Alto Networks now reports exploitation of internet-exposed management interfaces. This is a material change from its assessment in last week's issue. Check the installed PAN-OS branch against the vendor's current fix table, restrict management access and investigate possible compromise. Vendor advisory.
- CISA added the PHP and Brotli flaws to its known-exploited catalog. A fixed package on a host does not necessarily update the runtime inside a container or self-contained application. Verify what is actually running, including supplier-managed systems. Microsoft's October 30 guidance and NHS England's Brotli alert.
- A final federal health IT rule changes certification requirements for decision support. ONC finalized removal of requirements for access to certain source attributes and for predictive intervention risk management from its certification criterion, effective December 28. Clinical and procurement teams should ask suppliers what evidence and monitoring they will continue to provide. Federal Register.
- HHS settled a ransomware investigation involving Lehigh Valley Health Network. The $800,000 agreement follows a 2023 breach and includes a three-year corrective action plan. OCR cited potential failures involving risk analysis, system-activity review and timely notifications; LVHN did not admit liability. HHS announcement.
- FDA clarified what users should do about Nova's Gen 2 hospital glucose meters. If an alternative is available, stop using an affected meter until it is updated. Facilities without one should follow the full interim instructions, including two patient-identity checks. FDA notice.
UNM Health resumes clinical operations after diverting ambulances
UNM Health's October 26 cyber event affected the health system and its Health Sciences Center. From 12:30 to 2:30 p.m. local time, the system diverted ambulance traffic to other area hospitals. Outpatient surgeries and appointments were suspended for the rest of the day. UNM began bringing systems back in phases that afternoon and said care teams would reschedule affected patients.
UNM's October 27 assessment said some end-user devices were affected, but the event did not penetrate core systems or servers. On October 28, UNM said clinical operations across its health facilities were fully functional and classes and research had resumed. Those are UNM's statements. On October 27, it said an ongoing criminal investigation limited further public detail. The available notice does not establish the full extent of any data exposure, so claims by people taking responsibility should not be treated as verified findings.
UNM also warned patients and staff about possible follow-on scams, including false offers of compensation. It advised people not to engage with anyone claiming responsibility or provide personal or financial information. UNM's October 26–28 updates.
Continuity planning: A short diversion can still interrupt a day's appointments and shift patients to neighboring facilities. Review who can authorize a diversion, how receiving hospitals learn that capacity has changed, and who reconciles patients and procedures that need rescheduling. Separately, agree how patients can verify a genuine post-incident notice without following a link in an unexpected message.
Lehigh Valley settles OCR ransomware investigation
HHS announced on October 29 that Lehigh Valley Health Network paid $800,000 and agreed to a three-year corrective action plan to resolve an OCR investigation into a 2023 ransomware breach. HHS says the attack affected the protected health information of 248,359 people, including sensitive radiation-oncology photographs. The incident is from 2023; the settlement is this week's development.
OCR identified potential HIPAA violations involving risk analysis, regular review of information-system activity, disclosure and timely notification to individuals and HHS. The signed agreement states that LVHN does not admit liability. The corrective action plan applies to LVHN's legacy system and the entities listed in the agreement, not automatically to every part of its later parent organization. HHS announcement · Resolution agreement and corrective action plan.
Acquisitions and integrations deserve particular attention. The agreement says the incident involved an IT system of a physician group acquired in 2021. Security and privacy leaders should verify that acquired systems are included in the ePHI inventory and risk analysis, that someone reviews their audit activity, and that incident and notification responsibilities are assigned. The case-specific plan is not a new blanket deadline for other organizations.
South Carolina launches a rural-hospital cyber pilot
South Carolina, federal officials and industry partners launched Project Lifeline 250 on October 26. The governor's announcement describes a six-month pilot offering participating rural hospitals cybersecurity assistance at no cost. Its stated focus includes network defenses, backup technology to support operations during an incident and identification of high-risk medical and other technology. South Carolina governor's announcement.
The announcement describes planned work, not measured outcomes, and does not give a participant count or application instructions. Hospital leaders considering an offer should ask what is covered after the pilot, who maintains the equipment and access, and how security monitoring and incident support will be handed off when the six months end.
Exploited software: check the system that is actually running
Palo Alto now reports attacks on firewall management interfaces
Last week's issue reported Palo Alto Networks' then-current assessment that it knew of no malicious exploitation against its products and described an availability impact. On October 29, the vendor reported active exploitation of internet-exposed management interfaces and rated the issue critical. This supersedes its earlier product-specific assessment.
Network owners should match the installed PAN-OS branch to Palo Alto Networks' current fix table, restrict management access to trusted administrative systems and investigate exposed appliances for possible prior compromise. Patching does not establish that earlier access was legitimate.
PAN-OS applicability and hotfix details
The affected management surface includes the HTTPS web interface and XML API on PAN-OS firewalls and Panorama. The vendor says GlobalProtect portals, gateways and Clientless VPN are not affected by this issue. Risk is highest when a management interface is accessible from the internet.
The same hotfix generally addresses the PHP and Brotli issues. One exception is PAN-OS 11.2.10-h16, which fixes the PHP issues only; 11.2.10-h17 covers both. Check the vendor's current matrix for the installed branch.
Ivanti patches more flaws in an exploited remote-access chain
CISA added two Ivanti Connect Secure vulnerabilities, CVE-2026-111357 and CVE-2026-118527, to its known-exploited catalog on October 30. Remote-access owners should review the current Ivanti guidance even if the appliance received the October 13 update. Volexity documented an attack chain against a Connect Secure appliance and says Ivanti published a patch for the privilege-escalation flaw on October 29. Volexity's investigation · Rapid7's update and patch guidance.
Confirm the fix for the installed branch with Ivanti, then investigate exposed appliances for prior compromise. Volexity warns that a clean Integrity Checker result may miss this activity; network and memory forensics may be needed. Preserve evidence before recovery where feasible. The research does not establish that a particular healthcare organization was compromised.
PHP: known exploitation changes last week's status
CISA added PHP CVE-2026-109618 and CVE-2026-109619 to its known-exploited catalog on October 26. The PHP project says installations serving web requests are at risk. Application owners should verify the PHP instance actually serving each application, install the applicable vendor-fixed package and restart the relevant workers or web service. A corrected container image must be deployed, not merely downloaded. PHP guidance · Microsoft's deployment guidance.
The new KEV listing does not validate the earlier PHP2Shell-specific incident attribution that Unit 42 and Sophos retracted. Last week's issue described those retractions; they remain important. Unit 42's updated report · Sophos correction.
PHP fixed releases and deployment checks
The PHP project issued fixes in releases 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Check the appropriate distribution's fixed package where it backports fixes. On Windows, Windows Update does not update separately installed PHP. OpenEMR operators should verify the deployed image and the PHP instance serving the application. PHP's release guidance.
PHP's October 26 Windows packages have a -1 build suffix for the Brotli dependency update while the PHP runtime version stays the same. Check the package build as well as the version.
Brotli: look beyond Node.js
Brotli is a compression library used inside runtimes and applications. CVE-2026-111497 can corrupt memory when a program decompresses attacker-controlled data, potentially causing a crash, information disclosure or code execution. CISA added it to its known-exploited catalog on October 27. NHS England describes researcher-demonstrated code execution and exploitation attempts; it does not identify an affected NHS organization. NHS England · Node.js.
Ask application owners and suppliers where untrusted compressed requests or responses can reach an affected decoder. Update the applicable product and verify the running version after restart. Rebuild and redeploy containers or self-contained applications when they carry an affected runtime. An inbound filtering rule alone does not protect an application that fetches and decompresses a malicious response.
Brotli and Node.js release details
The Node.js project released fixes for its supported 22, 24 and 26 branches in versions 22.23.4, 24.22.1 and 26.12.1. Other products bundle Brotli and have their own advisories and update paths. A shared-runtime update alone does not update a self-contained application. Node.js release · Microsoft product guidance.
AI and health IT: ONC changes decision-support certification
ONC's HTI-5 final rule, published October 28, revises the health IT certification program. Among its changes, ONC will remove the certification criterion's requirements for source-attribute support and access for evidence-based and predictive decision support, and intervention risk management for predictive decision support. It retains other requirements, including support for selecting interventions and a feedback capability for evidence-based interventions.
ONC said it found insufficient evidence that the removed transparency requirements improved care or were being used to review the information. Commenters raised concerns that their removal could make it harder for providers to evaluate a tool's intended use, performance, limitations and risks. These are different positions recorded in the rule, not a finding that all decision-support systems are unsafe or that every other applicable obligation disappears.
The final rule takes effect December 28, 2026, except for specified amendments effective January 1, 2027. The decision-support amendments are in the main group. The rule addresses ONC certification; it does not by itself decide the requirements imposed by FDA or other authorities on every product. Final rule, including the decision-support discussion and effective dates · ONC overview.
Clinical governance and procurement teams should identify which decision-support tools inform care, then ask their suppliers for intended use, validation in relevant patient populations, known limitations, changes to the model and a route for reporting problems. Decide who reviews that evidence and who can suspend a tool when performance in the local setting is unacceptable. Put those expectations in purchasing and oversight processes rather than assuming certification alone supplies every answer.
Clinical engineering and medical device watch
Philips identifies products for PHP and Brotli review
Philips' October 28 Node2Shell advisory identifies specified Focal Point 2.1 and 2.2 releases among products that could be affected by the Brotli flaw. Its October 29 PHP advisory identifies several product families, including Advanced Visualization Workspace and IntelliSpace Portal, with product-specific conditions and mitigations. The advisories are vendor applicability assessments, not reports of compromised devices or patients. Philips security advisories.
Clinical engineering and the product owner should match the product and version to Philips' current advisory, then coordinate with the service team on the applicable action. Philips says changes to its products, including operating-system patches, should follow its product-specific validated and communicated procedures. Do not apply a generic runtime update to a medical product without that coordination.
FDA posts an older Illumina network-configuration recall
On October 30, FDA posted an open, classified Class II recall record for the Illumina NextSeq 550Dx in vitro diagnostic instrument, reference 20005715, all lots. The record says Illumina initiated the action on May 8, 2024, and retrospectively reported a cybersecurity vulnerability in the communication protocol between devices and customer-provided infrastructure. The vulnerability may compromise data transmission. The posting date is new; the underlying action is not.
The FDA record says the manufacturer's 2024 instructions asked customers to read its cybersecurity guidance, work with IT to select and implement an appropriate secure protocol for each affected network-connected product, and complete the verification form. Laboratory, clinical engineering and IT owners should confirm whether their device is in scope and whether that action was completed. Do not infer an attack or a new recall initiation from the database posting. FDA record Z-0320-2027, event 99957.
Nova StatStrip Gen 2.0 remains on the active watch
FDA's October 20 notice, updated October 30 to clarify recommended actions, concerns the StatStrip Glucose Hospital Meter System Gen 2.0, models 63685 and 66739, on all firmware. Previously scanned patient information can remain on screen and cause a result to be assigned to the wrong record; the glucose measurement itself remains accurate. This is a device safety issue, not a reported cyberattack.
If an alternative is available, FDA says to stop using the affected meter until it is updated. If none is available, follow all interim steps: enable patient-ID validation where integrated admission, discharge and transfer data support it, configure automatic operator logoff after each test, and verify patient identity both after scanning and when the result appears. Flag or remove misassigned results under the facility's correction process and promptly notify the treating team. Nova's planned phased November software rollout was not an available fix in the checked notice. CCD display until November 8 is an editorial watch date, not a recall termination or manufacturer deadline. FDA scope and instructions.
Priority CVEs
- Palo Alto Networks and PHP: Palo Alto Networks reports active exploitation of internet-exposed PAN-OS management interfaces affected by the two PHP issues. Restrict management access, install the fix for the installed maintenance line and investigate possible earlier access. The GlobalProtect portal and gateway are not the affected management interface. Palo Alto Networks advisory
- Brotli: Check applications that decompress untrusted content, including affected Node.js deployments. Apply the product-specific fix or migrate unsupported versions. A CISA catalog entry establishes known exploitation of the vulnerability, not proof that every affected product has been attacked. Node.js security releases
- Ivanti Connect Secure: Two additional vulnerabilities have joined CISA's known-exploited list in the established Connect Secure attack chain. Follow the current release guidance and investigate signs of compromise. A clean integrity check alone is not proof that an appliance is safe. Canadian Centre for Cyber Security and Volexity investigation
- GitLab: An unauthenticated attacker can execute code on affected self-managed GitLab installations. Upgrade the installed release branch; GitLab.com and Dedicated were patched. GitLab release
- Cisco ASA and FTD: A crafted request can reload appliances with certain SSL remote-access VPN and secondary-authentication configurations. Match the installed release to Cisco's fix. The stated impact is denial of service, not remote code execution. Cisco advisory
CVE Tracker
Open a record for affected versions and response. CCD display dates control when an item leaves this newsletter's active list; they are not patch deadlines or proof that the issue is fixed. Earlier records remain in the October 26 issue. Display dates for new exploitation-watch entries are under review because their original CCD tracking dates were not recovered. Exploitation status and federal due dates were checked against the CISA KEV catalog, version 2026.10.30, on November 2. Eleven entries with a November 2 drop date leave the active view today; their history remains in the October 26 issue. Leaving the tracker does not mean an issue is fixed.
PHP out-of-memory handling: CVE-2026-109618: Unauthenticated code execution was demonstrated with certain Apache configurations. Known exploited; update the applicable PHP or appliance release. CCD display until November 4.
PHP powers web applications, including some patient-record and scheduling systems. Researchers demonstrated unauthenticated code execution through the out-of-memory handling flaw using Apache's mod_php; build and configuration influence exploitability. Supported PHP branch fixes are 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Verify the software actually running the application, not just an available image. PAN-OS owners should match the maintenance line to Palo Alto Networks' advisory, restrict management access and investigate possible prior compromise. PHP disclosed and released fixes October 21; CISA added the CVE October 26, with an October 29 federal due date; Palo Alto Networks updated its exploitation assessment October 29. PHP CNA severity: CVSS 4.0 9.2. The November 4 CCD date is a preserved bounded editorial decision, not a recovered first-tracked date. PHP releases · Palo Alto Networks
PHP request-state handling: CVE-2026-109619: Stale request state can persist after fatal errors. Known exploited; install the complete request-state fix. CCD display until November 4.
This distinct PHP flaw can leave stale request state after fatal error handling. Install PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12 in the applicable supported branch, or the relevant vendor appliance fix. The session-setting mitigation for CVE-2026-115560 does not replace this update. PHP released fixes October 21; CISA added this issue October 26, with an October 29 federal due date. Palo Alto Networks confirmed attacks against internet-exposed management interfaces in its October 29 update. PHP CNA severity: CVSS 4.0 9.2. The November 4 date is the prior bounded CCD decision, not a recovered first-tracked date. Do not treat earlier retracted attribution as confirmed. PHP releases · Palo Alto Networks
PHP session handling: CVE-2026-115560: The issue affects a specific session-handler switch when upload progress is enabled. Check a narrow session configuration and apply PHP's interim setting. CCD display until November 6.
The issue concerns applications that switch from php_binary or php_serialize to php before session_start(), with session upload progress enabled. PHP recommends session.upload_progress.enabled=0 for that combination while a regular bugfix release is pending. This is not a blanket mitigation for the two other PHP issues. PHP's notice is dated October 23. A fixed release and severity score were not established in the checked notice; the issue was not found in the October 30 CISA catalog. PHP notice
Arista VeloCloud Orchestrator: CVE-2026-114625: A read-only account may gain operator privileges. Known exploited; update customer-managed orchestration servers. CCD display until November 8.
Customer-managed VeloCloud Orchestrator is affected on the 5.2 branch before 5.2.3.18, 6.1 before 6.1.3.10 and 6.4 before 6.4.2.12. Network access and an authenticated session are required, but an Enterprise Read Only account is sufficient to gain operator privileges. Arista-hosted instances, including Dedicated, were patched; Edge and Gateway are unaffected. Upgrade the matching branch and restrict management access while doing so. If compromise is suspected, preserve Arista’s specified logs and filesystem evidence before remediation where feasible. Arista published its advisory October 22; CISA added the issue October 23 with an October 26 federal due date. Arista severity: CVSS 3.1 9.9 and CVSS 4.0 9.4. First documented CCD tracking was October 25. Arista advisory
Nextcloud built-in CODE: CVE-2026-110447: An attacker can run commands while the built-in CODE component is stopped. Known exploited; update or remove the built-in CODE app. CCD display until November 8.
The richdocumentscode app before 26.4.303 is vulnerable while its built-in CODE component is stopped, such as during a restart or crash. An unauthenticated attacker can execute commands as the web-server user. Upgrade the app to 26.4.303 or later, or remove it; merely disabling it is insufficient. Nextcloud 29 or earlier requires a host upgrade or app removal. Standalone Collabora Online is unaffected. The issue was publicly reported September 11, with a formal advisory October 14; CISA added it October 23, with an October 26 federal due date. The advisory reports CVSS 4.0 9.2. First documented CCD tracking was October 25. Collabora advisory
Brotli decompression: CVE-2026-111497: Untrusted Brotli data can corrupt memory. Known exploited; assess reachable decompression and update affected products. CCD display date under review.
Processing untrusted Brotli data can corrupt memory; consequences depend on the application. Node.js fixed its supported 22, 24 and 26 release lines in 22.23.4, 24.22.1 and 26.12.1, respectively. End-of-life versions remain affected and need migration. On PHP for Windows, exposure through cURL's automatic HTTP-response decompression depends on that option being enabled; check the rebuilt package and dependency, not only the unchanged PHP runtime version. The Node releases appeared October 21; CISA added the issue October 27, with a November 10 federal due date. Google CNA severity: CVSS 4.0 9.2. CCD had tracked the issue by October 28, but the first tracking date is not established. Node.js · PHP
Ivanti Connect Secure privilege escalation: CVE-2026-111357: Local privilege escalation is part of the attack chain. Known exploited in a Connect Secure chain; patch and investigate. CCD display date under review.
This local privilege-escalation issue is one component of a chain affecting Ivanti Connect Secure. Follow the current vendor release guidance and supported upgrade path, and investigate possible prior access. The Canadian advisory lists current release thresholds, but the complete per-CVE vendor applicability matrix could not be independently retrieved. Volexity updated its investigation on October 29 to say a privilege-escalation patch was available; CISA added this CVE October 30, with a November 2 federal due date. Published numeric scores differ, so none is selected here. A clean integrity check alone does not establish that no compromise occurred. Canadian advisory · Volexity
Ivanti Connect Secure file placement: CVE-2026-118527: Authenticated remote file placement is part of the attack chain. Known exploited in the Connect Secure chain; follow the current vendor release guidance. CCD display date under review.
This issue permits authenticated remote file placement and can be combined with other flaws in the established chain. CISA added it October 30, with a November 13 federal due date. Select the supported release with Ivanti and investigate possible prior access; the complete per-CVE vendor matrix and a severity score were not independently established. The older CVE-2026-104935 is chain context here, not a reset of its retired standalone CCD entry. Canadian advisory · Volexity
GitLab self-managed CI/CD: CVE-2026-97229: An unauthenticated attacker can execute code through CI/CD regular expressions. Known exploited; update self-managed GitLab. CCD display date under review.
An unauthenticated attacker can execute code through malicious CI/CD regular expressions. Affected self-managed CE and EE releases are 19.2 before 19.2.8, 19.3 before 19.3.5 and 19.4 before 19.4.2. GitLab.com and Dedicated were patched. Install the applicable branch release and review the vendor's detection guidance. GitLab released fixes October 12 and published the CVE October 13; CISA added it October 29, with a November 1 federal due date. GitLab CNA severity: CVSS 3.1 10.0. The KEV addition is new; the underlying disclosure is not. GitLab release
Cisco ASA and FTD remote-access VPN: CVE-2026-76418: A crafted request can force configured VPN appliances to reload. Known exploited; patch applicable VPN appliances to prevent attacker-triggered reloads. CCD display date under review.
An unauthenticated request can trigger a device reload when the SSL remote-access login is reachable and the relevant tunnel group uses secondary authentication. The issue causes denial of service, not remote code execution. Match the installed ASA or FTD line to Cisco's software table. Cisco lists no workaround; disabling secondary authentication as a temporary mitigation reduces authentication security and requires a deliberate risk decision. Cisco published its advisory October 28; CISA added the issue October 29, with a November 1 federal due date. Cisco severity: CVSS 3.1 8.6. Cisco advisory and version table
Linux kernel: CVE-2026-46300: Affected kernels can permit local privilege escalation. Known exploited; apply the distribution's fix and verify the running kernel. CCD display date under review.
The Fragnesia flaw can allow local privilege escalation through a shared page-cache and ESP-in-TCP path. Not every Linux build includes the affected component. Apply the vendor's distribution-specific update and confirm the running kernel after any required restart. Public reporting began May 13; CISA added the issue October 28, with an October 31 federal due date. The Linux CNA and Red Hat report CVSS 3.1 7.8. The catalog addition is not a new October disclosure. Red Hat · Canonical
VMware ESX: CVE-2026-41709: A malicious administrator can bypass expected audit logs. Known exploited; update affected ESX systems to protect audit visibility. CCD display date under review.
A malicious administrator can perform certain actions without generating expected logs. This is not an unauthenticated host takeover. Broadcom lists ESX fixes including 9.1 build ESXi-9.1.0.0-25370933, 9.0 build ESXi-9.0.2.0100-25595025 and 8.0 build ESXi80U3j-25429389; select the correct product and upgrade path from the advisory. Broadcom disclosed the issue July 29 and updated its advisory August 19; CISA added it October 28, with a November 11 federal due date. Broadcom's CVSS 3.1 score is 2.7. Broadcom advisory
Adobe Commerce and Magento: CVE-2026-48356: Dangerous file upload is reachable without authentication and requires user interaction. Known exploited; apply the applicable commerce security update. CCD display date under review.
The dangerous-file-upload issue can be reached without authentication but requires user interaction. Check the Adobe Commerce or Magento deployment and its specific July 2026 security-update package; the B2B and Events components have separate mappings. This is not a generic electronic health record exposure. Adobe published the bulletin July 14 and updated it August 11; CISA added the issue October 27, with a November 10 federal due date. Adobe's bulletin and CNA record disagree on the numeric CVSS score, so no unqualified score is used here. Adobe advisory
FDA Recall Tracker
These notices concern device safety and care continuity. Match the exact device or kit to the FDA record. A CCD display date only governs this newsletter's active view; leaving the tracker does not end a recall. Dates for newly added notices remain under review where the prior CCD tracking anchor is unavailable. FDA sources were checked November 2, 2026.
Nova StatStrip Glucose Hospital Meter Gen 2.0: Results can be assigned to the wrong patient or quality-control record. Class I correction; use an alternative meter if available and follow FDA's identity checks. CCD display until November 8.
Models 63685 and 66739 on all firmware are affected; earlier Gen 1.86 models are excluded. A correct glucose result may be assigned to the wrong patient or quality-control record. If an alternative is available, stop using the affected meter until it is updated. Otherwise, enable patient-ID validation where admission, discharge and transfer integration supports it, set automatic operator logout after each test, and verify identity both after scanning and when the result appears. Immediately notify the administrator about a misassigned result; flag or remove it under facility procedures and promptly notify the treating team. The November software rollout remains planned, not confirmed available. FDA updated its instructions October 30. This is a correction, not a removal. FDA notice
Medline ChloraPrep convenience kits: Affected kits contain applicators with potential fungal contamination. Class I removal; match affected lots and destroy the entire kit. CCD display until November 10.
Specific Medline kits contain affected ChloraPrep applicators with potential fungal contamination. Match the kit and lot to FDA's workbook, quarantine affected kits, complete the response form and destroy the entire affected kit, not only the applicator. Do not extend the action to unrelated kits. Medline sent its customer letter August 11; FDA issued the Class I communication October 13. FDA notice and affected-kit list
AVID IV Start Kit: The affected kit contains an applicator with potential fungal contamination. Class I removal; quarantine and destroy the affected whole kit. CCD display until November 11.
Match kit KRIV26-02, lot 1658437, UDI 10809160460481. It contains an affected ChloraPrep applicator with potential fungal contamination. Quarantine the kit, complete the response form and destroy the entire affected kit. Do not generalize the action to unrelated AVID products. AVID issued its customer letter August 20; FDA issued the Class I communication October 14. FDA notice
HemosIL AcuStar HIT-IgG(PF4-H): Negative bias may cause false-negative HIT antibody results. Class I removal; destroy affected assay lots and plan alternative testing. CCD display date under review.
Parts 0009800127 and 0009802028, lots B40005, B40006, B38062 and B38063, are affected. Negative bias may cause false-negative heparin-induced thrombocytopenia antibody results. Destroy remaining affected product, document destruction on the response form and arrange alternative testing. Laboratory leadership and the treating clinician decide whether prior results need review or retesting. Two lots expired November 1, but earlier results can still matter. FDA posted the notice October 30; that date is not the recall's initiation date. FDA notice
Medline beds and accessories: The beds and accessories present fire and entrapment hazards. FDA early alert; follow updated instructions while arranging an authorized repair or replacement. CCD display date under review.
The action covers Medline-brand beds and associated accessories, with fire and entrapment hazards. The October 24 updated instructions allow continued use pending an authorized repair or replacement: unplug except while repositioning, do not use extension cords and have a second person assist when possible. Do not independently repair or modify the equipment. Unplugging does not by itself resolve entrapment risks. Contact Medline about the applicable remedy. FDA posted the early alert October 29; the alert does not establish a Class I classification. FDA early alert
B. Braun Streamline Bloodline Set for Dialog+: Inadequate connector bonding can cause a bloodline to leak or detach. FDA early alert; stop using, quarantine and return the three affected lots. CCD display date under review.
The affected model is SL-2010M2096, lots A2600099, A2600128 and A2600136. Inadequate connector bonding can allow a bloodline to leak or detach, potentially interrupting dialysis and causing blood loss or air entry. Inform users, cease use, quarantine and return affected product. FDA posted the early alert October 27; the notice does not establish a Class I classification. FDA early alert
Illumina sequencing instruments and servers: The records describe an older network-protocol cybersecurity issue. Five Class II records cover NextSeq 550Dx, MiSeq Dx, NovaSeq 6000Dx, DRAGEN Server for NextSeq 550Dx and VeriSeq Onsite Server V2. Confirm network configuration with laboratory IT and Illumina. CCD display date under review.
FDA posted the five records October 30, 2026; Illumina initiated the correction May 8, 2024. The records describe a retrospectively reported network-protocol cybersecurity issue, not a newly reported attack or a new 2026 recall initiation. Check the specific product and all-lot scope, follow the manufacturer's cybersecurity guidance on secure network configuration, and complete its verification form. The affected products are NextSeq 550Dx, REF 20005715; MiSeq Dx, REF DX-410-1001 or 15036706; NovaSeq 6000Dx, REF 20068232; DRAGEN Server for NextSeq 550Dx, REF 20086130; and VeriSeq Onsite Server V2, REF 20047000. FDA event index · NextSeq · MiSeq · NovaSeq · DRAGEN · VeriSeq
Sources and scope
This issue uses the primary incident notice, regulator and vendor advisories linked with each story. The reporting window is October 26 through November 1; source checks on November 2 are identified above. Product status and fix tables can change, so confirm the current notice for the exact deployment before acting. FDA's Illumina entry was posted this week but describes a 2024 action. No patient or organization should be assumed compromised solely because a product is affected or an exploit is known.