26 October 2026
Malware found in LiteLLM’s AI connection software; Quest restores lab-system access
Which passwords and access keys may need replacing, what Quest’s restored portal means, and how to check that OpenEMR’s corrected software is actually installed.
October 26, 2026 · Reporting week: October 19–25 · Reporting cutoff: October 26, 04:00 UTC. Status checks and later verification are distinguished in Sources.
CISO Quick Read
LiteLLM’s AI connection software was distributed with malware. LiteLLM connects applications to AI services. Platform and supplier owners using it for clinical documentation or other workflows need to identify which software was installed and which access keys or passwords it could reach. The corrected investigation traces the October 21 malicious releases to an exposed key that remained valid and stolen credentials. Recovery includes rebuilding affected systems, replacing reachable credentials and investigating their use. Affected downloads and recovery.
Quest restored access through its Quanum laboratory portal. Quest’s October 23 evening notice reported restoration of Quanum Lab Services Manager and the systems paused as a precaution. Core operations and direct connections to laboratory and medical-record systems were unaffected. The investigation into affected patient information continued. Restoration and the remaining privacy questions.
OpenEMR has made corrected software available; operators still need to install it. OpenEMR supports patient records, scheduling and billing. Application and hosting owners should verify the PHP software actually running the application. The publisher’s updated software package does not update an existing installation by itself. Unit 42 has retracted its earlier PHP2Shell-linked incident update. Applicable fixes and the correction.
Arista’s VeloCloud network-management software is being exploited. Organizations or suppliers using it to manage connections between sites should identify the responsible network operator and installed version. An attacker with management web access and a signed-in account, even Enterprise Read Only, can gain operator privileges. Arista-hosted management servers are patched; Edge and Gateway components are unaffected. Affected installations and updates.
University Hospitals reported appointment and elective-procedure rescheduling. Its later October 23 statement, reported by Cleveland19, expected some effects into the week of October 26. Organizations depending on UH referrals or services should use its current scheduling channels to confirm affected arrangements. What UH has said.
Priority CVEs
PHP web applications — CVE-2026-109618 / CVE-2026-109619Not in CISA KEV · Original PHP2Shell fixes available · Separate session issue below
PHP runs the server-side code behind many web applications. OpenEMR uses it for electronic patient records, scheduling and billing. Application and hosting owners running OpenEMR need to establish which PHP installation actually serves it before choosing the update and planning any interruption to those functions.
PHP’s October 21 security release fixes the original two PHP2Shell flaws in 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Researchers demonstrated code execution without logging in, using Apache’s mod_php component. The attacker’s code runs with the web-worker account’s access. PHP builds, extensions, front-end servers and memory allocation affect reliability; the demonstration does not establish identical exploitability across all configurations.
OpenEMR’s October 22 follow-up reports corrected container images, the software packages used to create running application instances: 8.3.0 and 8.2.0 use PHP 8.5.12, the republished 8.4.1/latest image uses 8.5.12, and the 8.0.0.3 line uses 8.4.27. Those packages must actually be deployed. Verify the installed image, its content fingerprint (digest), and the PHP version serving OpenEMR. A PHP version check on the host server can read a different installation from the one the application uses.
The exploitation record has changed. Unit 42’s October 25 update explicitly retracts its October 23 PHP2Shell-linked post-compromise update. It observed an attack against a European government agency in a vulnerable PHP application context, but could not confirm initial access through these CVEs. Sophos separately retracted its successful-exploitation claim. Researcher demonstrations and attempted activity do not establish a successful compromise at a healthcare organization.
CVE-2026-115560 is separate. This issue concerns how PHP saves and restores user-session data. PHP’s October 23 advisory describes applications configured with php_binary or php_serialize that switch to php before session_start(), with upload progress enabled. PHP recommends session.upload_progress.enabled=0 for that combination, pending a regular bugfix release. No fixed release or date was stated in the checked notice. This setting does not replace the original two flaws’ security updates.
PAN-OS patch update, checked October 26 at 09:43 UTC after the reporting cutoff: PAN-OS runs Palo Alto Networks firewalls and Panorama management systems. Network owners using these systems to control clinical-network connections should match their installed maintenance line to the vendor’s update table. Its October 26 changelog confirms released fixes 11.1.4-h38, 11.1.6-h40, 11.1.10-h36 and 11.1.13-h16. The October 25 entry confirms 10.2.18-h13, 11.1.16-h4 and 11.2.10-h16. Exact release times are not stated; other maintenance lines retain estimated dates. The vendor assesses management-interface availability impact and reports no known malicious exploitation against its products. PAN-OS code execution is not established. Plan the applicable update under change control and restrict management access to trusted systems while updating. PAN-OS affected and fixed versions.
Patching the device or system addresses the immediate vulnerability but it does not tell you if it had been previously compromised. Preserve relevant evidence and assess prior access separately when the deployment’s exposure warrants investigation.
PHP announcements and version guidance · OpenEMR image follow-ups · Unit 42’s corrected brief · Tracker records
Arista VeloCloud network management — CVE-2026-114625Known exploited — CISA KEV · Customer-managed installations need the applicable fix
Arista VeloCloud Orchestrator is the management server for network connections between sites. A healthcare network team or managed service provider may use it to configure links between hospitals, clinics and other facilities. The responsible network operator should identify who hosts the Orchestrator and which software branch is installed.
Arista confirms active exploitation of SQL injection in affected customer-managed, on-premises Orchestrators. This flaw lets an attacker manipulate database queries and gain operator privileges. The attacker needs management web access and a signed-in account; an Enterprise Read Only account is enough. Arista-hosted management servers, including Dedicated Orchestrators, are patched. Edge and Gateway components are unaffected.
Unauthorized operator access could change the connectivity the system manages. Apply the branch-specific vendor fix. Restrict management access to trusted administrative networks while the change is pending, and investigate suspicious management activity. Management restrictions do not remove the underlying flaw.
Nextcloud document editing — CVE-2026-110447Known exploited — CISA KEV · Update built-in CODE to 26.4.303+ or remove it
Nextcloud is file-sharing and collaboration software. Its built-in CODE app uses Collabora technology to edit documents in the browser. Providers or suppliers using that combination for referral documents or other sensitive files should have the Nextcloud administrator establish which app and version are installed.
The flaw affects richdocumentscode before 26.4.303 when built-in CODE is not running, including restart, upgrade or crash intervals. An attacker without a login can inject commands that run with the web-server account’s access. Standalone Collabora Online is unaffected.
The administrator should update to a fixed supported combination or remove the app. Disabling it is insufficient. Nextcloud 29 or earlier requires upgrading Nextcloud or removing the app; an offered 26.4.104 build is still below the fixed version. October 23 KEV inclusion is this week’s development, not a new disclosure. The impact on shared files depends on what the web-server account can access.
GlobalProtect remote access — CVE-2026-0257 campaign updateKnown exploited — CISA KEV · October 19 ransomware update to a May flaw
GlobalProtect connects staff and suppliers to an organization’s network, potentially including clinical systems. Network owners should check the sign-in portals and remote-access gateways with Authentication Override enabled (saved sign-in cookies) and the vendor’s certificate conditions. Unit 42’s October 19 update reports Qilin and Inc ransomware operators attempting to exploit CVE-2026-0257, disclosed and patched in May. The report does not establish that every attempt succeeded. Apply the May fix for the installed software version. Coordinate the update across all GlobalProtect sign-in portals and remote-access gateways that issue or accept those saved sign-in cookies, and plan for users to sign in again after the upgrade.
Unit 42 campaign update, October 19 at 23:00 UTC · Vendor exposure conditions and fixed-version matrix · CISA KEV record. Checked October 26 at 12:53 UTC.
Healthcare Incident Watch
Quest restores its laboratory portal while investigating patient-information exposure
Quanum Lab Services Manager gives users a route to Quest laboratory orders and results. Organizations exchanging this information with Quest need to distinguish portal access from direct connections between their laboratory or electronic medical-record systems and Quest.
Quest became aware of unauthorized activity involving Quanum LSM on October 21 and disclosed it in an October 22 filing. Its October 23, 7 p.m. ET notice said Quanum LSM and the systems paused as a precaution had been restored. Core operations and direct LIS/EMR interfaces were not impacted.
Quest said some patient records and personal information were affected; the scope and affected population remained under investigation. It reported no access to two other Quest services, Essential Insights or LabHQ, and explicitly said the incident was unrelated to PHP. The SEC filing was under Item 8.01, not a declaration under the separate material-cybersecurity-incident item.
A restored portal, an unaffected direct connection and an unfinished privacy investigation require different follow-up. Service owners should establish which route their organization uses; privacy teams should follow the information investigation separately.
University Hospitals disconnects systems and reschedules some care
University Hospitals in Ohio detected unusual server activity on October 22 and disconnected systems. In its later October 23 statement reported by Cleveland19, UH said some appointments and elective procedures were being rescheduled, some external connections had returned, and effects were expected into the following week.
The institutional website directs patients to telephone scheduling and referral options. The available statements do not confirm ransomware, patient-information exposure or a connection to the Quest incident.
Where an organization depends on UH referrals or services, the team coordinating that care should use UH’s current scheduling channels to confirm affected arrangements.
Cleveland19’s report carrying UH’s statement · UH service information
Parkview reports services restored after taking its network offline
Parkview Health’s MyChart portal lets patients view records, message care teams and manage appointments. Becker’s October 19 report said Parkview took its network offline after suspicious activity and first notified patients October 18; the cause was not confirmed as a cyberattack. In an undated banner checked October 26 at 12:57 UTC, Parkview says all services have been restored and no patient information was compromised. This is Parkview’s statement, not independent validation. The banner leaves unclear when restoration occurred and whether that status was known at the issue’s 04:00 UTC cutoff.
Parkview’s current service statement · Parkview MyChart and current banner · October 19 report of the earlier shutdown
BASS notifies patients after its September investigation
BASS Medical Group’s October 22 notice describes suspicious activity discovered around September 4 and a September 22 determination that information may have been accessed or acquired without authorization. Potentially affected information includes treatment or billing codes and health-insurance information, with the details varying by person.
BASS reported no evidence of misuse. The October notice concerns September activity. It does not confirm a patient count, ransomware or care disruption. Individual notices explain which information and assistance apply.
AI & Clinical Automation
LiteLLM’s AI connection software carried malware after an old access key remained valid
LiteLLM connects applications to AI services. Its connection layer is often called a gateway. These connections use credentials: access keys or passwords that let software use an AI service. A platform or supplier owner using LiteLLM for clinical documentation or another healthcare workflow needs to know which version ran and what other keys or information it could reach. Supporting a healthcare workflow does not itself establish access to medical records.
LiteLLM’s October 23 attack-chain report replaces the initial logging explanation. A master key exposed publicly on May 27 was never disabled. The attacker used the Agent Platform API, a software interface, on October 10 to obtain a GitHub CLI token with organization-owner privileges. The attacker then obtained more credentials through the automated build and release systems (CI). Changes to release protections and a lookalike repository enabled malicious signed software to be published on October 21. A valid software signature did not establish that the release was safe.
Exposure depends on the exact software installed and where it came from. The vendor identifies seven malicious prebuilt Python packages (PyPI wheels), litellm==1.107.0, available from 11:39:51 until removal by 13:23 UTC on October 21. It also identifies affected container-image tags v1.107.0, latest, main-latest and main-stable. These images package software for running services. Docker Hub’s window was 11:46:56–14:20 UTC; corresponding GitHub Container Registry (GHCR) downloads were unavailable by 13:51. The official GitHub source-code tag lacked the malicious files. The enterprise exemption concerns the private download registry, not every enterprise customer.
Ask the service owner for the installed package or image, its content fingerprint (digest), the exposure window and the credentials the software could reach. Recovery guidance warns that starting Python, including its package installer pip, can run the malware again. Rebuild affected environments, replace reachable keys and passwords, and investigate their subsequent use. Installing a clean package alone does not establish recovery; absence of the reported marker file does not prove an environment is clean. No named healthcare victim or exposure in the reader’s organization is established by this report.
Corrected attack chain · Affected downloads and recovery guidance · Original incident report and startup warning
Anthropic’s health examples leave outcomes and hosting questions open
Anthropic’s AI systems are being tested in health-information and research workflows. Its 2026 Public Benefit Report describes company-reported work on Burkina Faso health dashboards and Ebola monitoring and modeling in the Democratic Republic of Congo. The report also acknowledges that much of this work is early, evidence of intended health outcomes is missing, and local hosting cannot satisfy every country’s data-location requirements. These are not independently validated clinical-benefit findings. The report’s exact publication day is not established.
Healthcare buyers evaluating such a service should ask what improved in the actual workflow, who verifies the result, where data resides and who responds when the system fails. Access restrictions should be technically enforced. Ask which systems the model can reach, which actions need a person’s approval and how the deployment isolates network access. These are procurement questions, not claims that the report proves the controls were present in every example.
Anthropic’s report · Health examples and limits, pages 15–17
Regulatory & Privacy
FDA announced final guidance on prescription-drug apps and software on October 20, followed by its October 21 Federal Register notice. It explains how drug-labeling requirements apply to information produced by software distributed by or for a drug sponsor, including connected and standalone functions. Drug-software product and regulatory teams should distinguish that scope from the hospital applications they operate. This is nonbinding guidance, not a new cybersecurity rule or a blanket hospital-app deadline. FDA final guidance · October 21 availability notice
Active / Ongoing
FDA device-guidance priorities for fiscal year 2027: comments requested by November 30Details
FDA’s device center is seeking feedback on which guidance it should develop or publish. Its A-list, B-list and under-construction list identify different priorities. Device manufacturers, providers and researchers can suggest priorities, policy topics or additional guidance needs. These are development and publication plans, not issued guidance.
U.S. submission date: November 30, 2026, docket FDA-2012-N-1021. The FDA page does not specify a closing hour or time zone. Checked October 25.
FDA priorities and comment instructions · Regulations.gov docket FDA-2012-N-1021
FDA robotically assisted surgical-device draft: comments due November 24Details
Robotically assisted surgical devices let a clinician operate surgical instruments through software-controlled equipment. This draft addresses nonclinical testing, clinical data and labeling for certain remotely operated systems. Manufacturers and clinical users can submit evidence relevant to premarket review. It is nonbinding, distributed for comment and not for implementation.
U.S. comment date: November 24, 2026, docket FDA-2026-N-9505. No closing hour or time zone is asserted here. FDA issued the draft in September; the Federal Register notice appeared September 25. Checked October 25.
FDA draft and submission instructions · Regulations.gov docket FDA-2026-N-9505
FDA autonomous and remotely operated device workshop: December 2–3; in-person registration closes November 23 or at capacityDetails
FDA's hybrid workshop will consider benefits and risks of robotic medical devices with autonomous or remote-teleoperation capabilities. Providers, manufacturers and patients can contribute experience with these systems. It is a public workshop, not a rule or compliance obligation.
U.S. event: December 2 and 3, 2026, 10 a.m.–4 p.m. Eastern Time each day. In-person registration closes November 23 or earlier at capacity; virtual registration remains open afterward. The agenda and pre-workshop materials were still forthcoming when checked October 25.
Standing Watch
U.S. cyberincident reporting under CIRCIA: rule still under reviewDetails
CIRCIA concerns reporting cyberincidents affecting critical infrastructure. Healthcare security and legal teams that may fall within the eventual scope should distinguish planning from a current reporting duty. The federal record lists a final-stage rule pending review by OIRA, the federal office reviewing the regulation, received October 1 under Executive Order 12866. That review does not make the rule effective. No publication or effective date is established by the record.
Status checked: October 26. Federal rule identifier (RIN): 1670-AA04.
HIPAA Security Rule proposal: pending; July 2027 is a planning target, not a compliance deadlineDetails
The HIPAA Security Rule sets safeguards for electronic protected health information. Healthcare organizations and their business associates should continue to follow the current rule while assessing HHS’s proposed cybersecurity changes. The Unified Agenda lists the action under Long-Term Actions, with a July 2027 final-action target and no legal deadline. HHS says the current Security Rule remains in effect during rulemaking.
Covered entities and business associates can compare the proposal with their safeguards while keeping proposed requirements separate from current duties. Status checked: October 25. Federal rule identifier (RIN): 0945-AA22.
Unified Agenda planning entry · HHS proposal and current-rule statement
Clinical Engineering & Medical Device Watch
Standing Watch
These are medical-device safety and care-continuity notices, not reports of cyberattacks. Match the exact device or kit to the FDA notice and follow its instructions. The CCD display date controls this newsletter’s active list only; leaving the list does not end a recall.
Philips Lumify ultrasound — Class I instructions correctionCCD display until: 2026-11-01
Philips Lumify is an ultrasound system. Clinical-engineering staff and care teams using it should identify the affected iOS or Android software versions and the connectivity or backup equipment available when scanning. FDA’s October 19 update reports Class I classification; the affected products and recommendations did not change. This is a correction to use instructions, not removal of the systems from use.
A software issue can require the ultrasound probe (transducer) to be registered again unexpectedly. Scanning cannot resume until that registration is completed over Wi-Fi or cellular access. A separate unstable USB connection can interrupt scanning. Philips is developing a registration update and investigating the connection issue; neither resolution has a confirmed release date in the notice.
Action: Follow Philips' instructions: use Lumify where Wi-Fi or cellular service is readily accessible unless a backup ultrasound device is immediately available, keep backup devices or modalities available for care, and circulate and post the customer notice. Check the FDA's exact iOS and Android version list.
Identity and dates: FDA event 99878; recall Z-0152-2027. Customer letter: September 24. Early alert: October 9. FDA database posting: October 16. Last material communication update: October 19. Latest saved database status: Open/Classified. Communication checked October 26.
CCD display until: 2026-11-01. This is a prospective editorial display date, not a Philips deadline or recall closure.
FDA Lumify scope and use instructions · FDA recall record Z-0152-2027
Nova StatStrip hospital glucose meter — Class I removalCCD display until: 2026-11-08
Nova’s StatStrip meters measure blood glucose in hospital care. Testing staff and the teams managing the meters should match the model and software to FDA’s October 20 notice: StatStrip Glucose Hospital Meter System Gen 2.0, models 63685 and 66739, on all firmware. Earlier models such as Gen 1.86 are excluded. Previously scanned patient or quality-control barcode information can remain on screen and assign a result to the wrong record. The glucose measurement itself remains accurate.
Action: If an alternative device is available, FDA says to stop using the affected device. If none is available, follow the specified mitigation steps: enable patient-ID validation where integration with admission, discharge and transfer (ADT) systems supports it, log the operator out after each test, and verify patient identity both after scanning and when the result appears. Report and correct misassigned results through the facility's process and notify the treating team.
Nova intends a phased software rollout in November 2026. That is a plan, not an available fix or guaranteed release date.
Identity and dates: FDA event 99546; individual recall record 221819. Recall initiated July 29; database posting September 11; revised customer notice October 5. Last material communication: October 20. Class I removal; no termination is established. Communication checked October 26.
CCD display until: 2026-11-08. This is a prospective editorial display date, not a Nova deadline or recall closure.
FDA StatStrip models and mitigation instructions · Nova customer correction notice · FDA individual recall record
Draeger VentStar neonatal breathing hoses — Class I removalCCD display until: 2026-10-30
Draeger’s VentStar Resus Neo hoses support neonatal respiratory care. Clinical-engineering and neonatal-care teams using model MP00310 should match the affected scope in FDA’s notice.
Action: Inspect before use and discard hoses with cracks or detachment.
Identity and dates: FDA event 99787. Last material update: October 2 Class I communication. Latest saved status: Open/Classified. FDA instructions checked October 25; no new material update or termination was established.
CCD display until: 2026-10-30, preserved from the prior watch. It is an editorial display date, not a vendor deadline or recall closure.
FDA VentStar affected hoses and inspection instructions · FDA event 99787
Medline procedure kits with ChloraPrep — Class I removalCCD display until: 2026-11-10
These Medline procedure kits contain BD ChloraPrep skin-preparation applicators. Supply-chain and clinical teams using the kits should match the full product and lot list before removal. FDA’s workbook lists 53 kit/lot combinations across 34 kit stock codes (SKUs). Potential Aspergillus penicillioides fungal contamination can cause serious infection. The revised whole-kit action does not apply to every kit in the earlier, broader notification.
Action: Check the full affected-product workbook, quarantine the listed affected kits, complete the response form, then destroy the entire affected kit.
Identity and dates: FDA event 99669. Customer letter: August 11. Database posting: September 14. Last material update: October 13 Class I communication. Recall confirmed; no termination established. FDA instructions checked October 25.
CCD display until: 2026-11-10, preserved from the prior watch. It is an editorial display date, not a vendor deadline or recall closure.
FDA Medline whole-kit removal instructions · FDA full affected-kit and lot workbook · FDA event 99669
AVID intravenous-line preparation kit — Class I removalCCD display until: 2026-11-11
AVID’s IV Start Kit supplies materials for preparing intravenous access. Supply-chain and clinical teams should match kit KRIV26-02, lot 1658437, unique device identifier (UDI) 10809160460481. It contains a recalled BD ChloraPrep applicator with potential Aspergillus penicillioides fungal contamination. Do not extend this action to unrelated AVID kits.
Action: Quarantine the affected kit, complete the response form, then destroy the entire affected kit.
Identity and dates: FDA event 99672; recall Z-3108-2026. Customer letter: August 20. Database posting: September 14. Last material update: October 14 Class I communication. Recall confirmed; no termination established. FDA instructions checked October 25.
CCD display until: 2026-11-11, preserved from the prior watch. It is an editorial display date, not a vendor deadline or recall closure.
FDA AVID kit scope and whole-kit removal instructions · FDA event 99672
CVE Tracker
Open a record for the product’s purpose, affected versions and response. CCD display until is when an item leaves this newsletter’s active list; it is not a patch or legal deadline.
New disclosures
PHP software for web applications — CVE-2026-109618
Details
PHP runs web applications, including OpenEMR’s patient-record, scheduling and billing functions. In an OpenEMR installation, the application and hosting owners should identify the PHP software actually serving users, including the installed container image and its digest, an identifier for that software package.
Affected: Researchers demonstrated code execution without logging in (unauthenticated code execution) through the out-of-memory cleanup flaw, using mod_php, the PHP component loaded into an Apache web server. Reliability depends on the software build and server configuration.
Response: Install PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12, or a later applicable fixed release, in the supported branch used by the application. A session-setting workaround does not replace this update. OpenEMR’s corrected downloadable images make the software available; operators still need to install and run the corrected package. The PHP priority item covers those images, PAN-OS’s separate product assessment and the explicit Unit 42 retraction.
Severity: CVSS 4.0: 9.2 (PHP CVE authority).
Release history: Original PHP security releases: 2026-10-21. OpenEMR image follow-up: 2026-10-22. PAN-OS fix availability was checked separately after the reporting cutoff.
Exploitation status: Not in CISA KEV at the 2026-10-26 check. CISA remediate-by: none listed.
Dates: Disclosure: 2026-10-21. Last material evidence update: 2026-10-26, PAN-OS patch-status check after the reporting cutoff; Unit 42’s retraction remains dated 2026-10-25. Earlier first CCD tracking and first newsletter appearance are unknown. CCD display until: 2026-11-04. This bounded display decision uses the earliest trusted owner lead, 2026-10-21; it is not a recovered historical tracking date.
PHP advisory, affected versions and CVSS · PHP security releases
PHP software for web applications — CVE-2026-109619
Details
PHP runs web applications, including OpenEMR’s patient-record, scheduling and billing functions. The application and hosting owners should identify the PHP software actually serving that installation and plan the application update. Making a corrected package available does not install it on an existing service.
Affected: This flaw leaves stale global request state, data retained in memory from request processing. It requires the complete PHP state-reset fix. Disabling upload progress addresses one demonstrated session path, not every original lifecycle path.
Response: Install PHP 8.2.35, 8.3.36, 8.4.27 or 8.5.12, or a later applicable fixed release, in the supported branch used by the application. Confirm the corrected software is actually running. Investigate suspected previous access separately from installing the update.
Severity: CVSS 4.0: 9.2 (PHP CVE authority).
Release history: Original PHP security releases: 2026-10-21. OpenEMR image follow-up: 2026-10-22. PAN-OS fix availability was checked separately after the reporting cutoff.
Exploitation status: Not in CISA KEV at the 2026-10-26 check. CISA remediate-by: none listed.
Dates: Disclosure: 2026-10-21. Last material evidence update: 2026-10-26, PAN-OS patch-status check after the reporting cutoff; Unit 42’s retraction remains dated 2026-10-25. Earlier first CCD tracking and first newsletter appearance are unknown. CCD display until: 2026-11-04. This bounded display decision uses the earliest trusted owner lead, 2026-10-21; it is not a recovered historical tracking date.
PHP state-reset advisory and fixes · Image deployment and explicit Unit 42 retraction
PHP web-application sessions — CVE-2026-115560
Details
PHP runs web applications; its session functions retain data between a user’s requests. The application or hosting owner should check whether a service supporting patient records or scheduling uses the specific session settings below before changing them.
Affected: Applications configured with php_binary or php_serialize that switch the session-data format to php before calling session_start(), with upload-progress tracking enabled. Using PHP alone does not establish this condition.
Response: The PHP notice recommends session.upload_progress.enabled=0 for that combination, pending a regular bugfix release. Establish whether the application switches its session-data format at that point before changing this setting. No fixed release or date was specified in the checked notice. The original two CVEs’ fixes do not establish resolution of this separate issue.
Severity: Numeric CVSS was not supplied in the PHP notice.
Release history: Informational advisory and conditional mitigation notice: 2026-10-23. No fixed release date was stated in that notice.
Exploitation status: Not in CISA KEV at the 2026-10-26 check. CISA remediate-by: none listed.
Dates: Disclosure: informational advisory 2026-10-23. Last material update: 2026-10-23. Historical first CCD tracking and first newsletter appearance are unknown. CCD display until: 2026-11-06. This bounded display decision is measured from the 2026-10-23 advisory, not an invented tracking history.
Arista VeloCloud network management — CVE-2026-114625
Details
Arista VeloCloud Orchestrator is the management server for connections between sites. A healthcare organization or its network provider may use it to manage links between clinics and central services. The network owner should identify who operates it and which software branch is installed.
Affected: Customer-managed VeloCloud Orchestrator (VCO; on-premises) 5.2.x before 5.2.3.18, 6.1.x before 6.1.3.10, and 6.4.x before 6.4.2.12. An authenticated session and network access to the web interface are required; an Enterprise Read Only account is sufficient. Arista-hosted VCO, including Dedicated, is patched; Edge and Gateway are unaffected.
Response: Upgrade to 5.2.3.18+, 6.1.3.10+ or 6.4.2.12+ within the matching software branch. Restrict management access while patching. If compromise is suspected, preserve the logs and filesystem evidence specified by Arista before remediation where feasible.
Severity: CVSS 3.1: 9.9; CVSS 4.0: 9.4 (Arista).
Release history: Fixed build release dates not established; vendor advisory published 2026-10-22.
Exploitation status: Known exploited — CISA KEV. Added 2026-10-23; CISA remediate-by: 2026-10-26.
Dates: Disclosure: 2026-10-22. Last material update: 2026-10-23 (KEV addition). First documented CCD tracking: 2026-10-25. First newsletter appearance: not established. CCD display until: 2026-11-08.
Updated exploitation watch
Nextcloud document editing with built-in CODE — CVE-2026-110447
Details
Nextcloud provides file sharing and collaboration; its built-in CODE app adds Collabora document editing. A provider or supplier using that app for shared referral documents depends on the document service and the files it can access. The collaboration-platform owner should check the installed app and Nextcloud versions.
Affected: The richdocumentscode document-editing app before 26.4.303 is affected while its built-in CODE editing component is not running, including restart, upgrade or crash intervals. An attacker without a login can inject commands that run with the web-server account’s permissions. Standalone Collabora Online is unaffected.
Response: Upgrade richdocumentscode to 26.4.303 or later, or remove it; disabling it is insufficient. Nextcloud 29 or earlier requires a Nextcloud upgrade or removal of this app. The app-store release offered to an old host may remain below the fixed version.
Severity: CVSS 4.0: 9.2 (Collabora).
Release history: Fix confirmed in the 2026-09-14 maintainer response; exact release date not established.
Exploitation status: Known exploited — CISA KEV. Added 2026-10-23; CISA remediate-by: 2026-10-26.
Dates: Disclosure: Public incident thread 2026-09-11; formal advisory 2026-10-14. Last material update: 2026-10-23 (KEV addition). First documented CCD tracking: 2026-10-25. First newsletter appearance: not established. CCD display until: 2026-11-08.
Collabora advisory · Earlier public report and maintainer response · Nextcloud app releases · CISA record
Continuing watch
Fortinet network and privileged-access administration — CVE-2025-61624
Details
These Fortinet products manage firewalls, web proxies, switches or privileged access. A provider using them to control clinic connectivity depends on their configurations and administrative files. The network or privileged-access owner should identify the actual product and release before choosing an update.
Affected: An authenticated administrator with at least read-write command-line interface (CLI) permissions can modify or delete files by escaping an intended file path, a flaw called path traversal. This is not unauthenticated remote access.
Response: Vendor-listed fixed releases: FortiOS 7.6.5/7.4.10; FortiProxy 7.6.5/7.4.12; FortiPAM 1.8.0/1.7.1; FortiSwitch 7.6.5/7.4.9; FortiSwitchManager 7.2.8/7.0.7, or appropriate later fixed releases. Follow the model and release-specific upgrade path. FortiProxy 7.4.12 has intermediate-upgrade and RADIUS network-sign-in compatibility cautions in its release notes.
Severity: CVSS 3.1: 5.4 (vendor CVE authority).
Release history: Fixed targets documented in the 2026-04-14 vendor CVE record; release dates vary by product and are not established here.
Exploitation status: Known exploited — CISA KEV. Added 2026-10-16; CISA remediate-by: 2026-10-19.
Dates: Disclosure: 2026-04-14. Last material update: 2026-10-16. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
Fortinet CVE record and solutions · Fortinet advisory · FortiProxy 7.4.12 release notes · CISA record
GlobalProtect remote-access software for Mac — CVE-2026-0315
Details
GlobalProtect is remote-access software that connects a device to an organization’s network. A managed Mac may use it to reach clinical or administrative applications. The endpoint-management team should check the Mac client version; this record does not call for changing every remote-access gateway.
Affected: A local user without administrator rights can gain root privileges, the highest level of control on the Mac. Affects macOS 6.3.0–6.3.3-h15 and 6.2.0–6.2.8-h14; Windows, Linux, iOS, Android and ChromeOS clients are unaffected.
Response: Install 6.3.3-h16 (6.3.3-1199) or 6.2.8-h15 (6.2.8-1084), or a later applicable version. No workaround is listed.
Severity: CVSS 4.0 base: 8.5; vendor threat-adjusted score: 5.9.
Release history: Vendor solution published 2026-10-14; exact build-release dates not established.
Exploitation status: Not listed in CISA KEV at the 2026-10-26 check; no CISA remediate-by: date listed.
Dates: Disclosure: 2026-10-14. Last material update: 2026-10-14. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
PAN-OS firewall management — CVE-2026-0322
Details
PAN-OS runs Palo Alto Networks firewalls, while Panorama provides centralized management. A provider may rely on these systems to control connections between clinical networks. The network-security owner should identify the installed release and restrict who can reach its management interface.
Affected: An authenticated attacker with high privileges and management-interface access can execute code on affected PA-Series, VM-Series and Panorama systems. Cloud NGFW and Prisma Access are unaffected.
Response: Fixed destinations include 12.2.4+, 12.1.10-h2+, 11.2.16+, 11.1.16-h3+ and 10.2.18-h12+ in the corresponding software branches. Earlier maintenance lines have separate hotfixes; use the vendor table for the installed line. Unsupported releases must move to a supported fixed release. Restrict management access to trusted internal systems while updating; this is mitigation, not the patch.
Severity: CVSS 4.0: 8.6 (Palo Alto Networks).
Release history: PAN-OS 11.2.16 released 2026-10-15; other hotfix-release dates not established here.
Exploitation status: Known exploited — CISA KEV. Added 2026-10-14; CISA remediate-by: 2026-10-17.
Dates: Disclosure: 2026-10-14. Last material update: 2026-10-15. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
BeyondTrust Remote Support — CVE-2026-102764
Details
BeyondTrust Remote Support lets IT staff and suppliers provide remote assistance to computers. A provider using it to maintain clinical workstations depends on that support connection. The support-platform owner should distinguish a customer-managed appliance from BeyondTrust’s hosted service before checking the patch.
Affected: Remote Support through 26.2.3 permits unauthorized file operations because it does not properly validate a message’s origin. The Remote Support vulnerability scope is separate from the precautionary Privileged Remote Access (PRA) recommendation below.
Response: Apply patch BT26-05-RS for 24.3.1–26.2.3 and verify installation, including automatic updates. Older installations must upgrade before applying it. BeyondTrust’s hosted Remote Support service was patched by 2026-10-09. Its 2026-10-16 incident update also recommends immediate precautionary BT26-05 patching of customer-managed Privileged Remote Access, a separate product for privileged remote connections, because of shared code. BeyondTrust reported no PRA exploit found in its internal testing. Follow the PRA-specific instructions; the Remote Support version matrix is not a PRA matrix.
Severity: CVSS 4.0: 9.3 (BeyondTrust).
Release history: Hosted-service patch applied by 2026-10-09; advisory issued 2026-10-15; customer patch-release date not established.
Exploitation status: Known exploited — CISA KEV. Added 2026-10-16; CISA remediate-by: 2026-10-19.
Dates: Disclosure: 2026-10-15. Last material update: 2026-10-16. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
BeyondTrust Remote Support advisory · 2026-10-16 incident update and PRA precaution · CISA record
Ivanti Connect Secure remote access — CVE-2026-104935
Details
Ivanti Connect Secure controls remote access to an organization’s network and applications. A provider may use it for staff or supplier access to patient-administration systems. The remote-access owner should establish the installed software line and its supported upgrade path.
Affected: The Ivanti CVE authority describes a way to bypass authentication before 25.1.3.0, excluding 22.7R2.14 and earlier. Do not generalize the affected range to every older release.
Response: Ivanti lists fixes 25.1.1.2, 25.1.3.0, 25.1.3.1 and 22.8R2.5 for the applicable software branches. Select the supported upgrade path for the installed line with Ivanti; an excluded older release is not an upgrade recommendation.
Severity: CVSS 3.1: 8.6 (vendor CVE authority).
Release history: Fix availability described in Ivanti’s 2026-10-13 notice; exact per-build release dates not established.
Exploitation status: Known exploited — CISA KEV. Added 2026-10-13; CISA remediate-by: 2026-10-16.
Dates: Disclosure: 2026-10-13. Last material update: 2026-10-13. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
Ivanti October release guidance · Ivanti CVE record · Ivanti detailed advisory · CISA record
AhsayCBS backup service — CVE-2026-105133
Details
AhsayCBS manages backups and recovery. A provider using it for patient-record or scheduling backups depends on that service when restoring operations. The backup-service owner should check which replacement hotfix is installed, because Ahsay corrected an earlier incomplete fix.
Affected: A flaw in login checks (authentication bypass) affects the v7/v8/v9/v10 installations covered by Ahsay’s correction. It can be combined with the command-injection flaw CVE-2026-105134.
Response: Use replacement hotfix 10.3.4.45 for affected v10, or 9.15.2.70 for affected v7/v8/v9, then reboot as directed. Hotfix access requires an existing partner account; do not assume a prior patch completed the repair.
Severity: Numeric CVSS not established in the retained vendor evidence.
Release history: Replacement-fix correction 2026-10-12; exact original release dates not established.
Exploitation status: Known exploited — CISA KEV. Added 2026-10-14; CISA remediate-by: 2026-10-17.
Dates: Disclosure: Not established. Last material update: 2026-10-14. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
AhsayCBS backup service — CVE-2026-105134
Details
AhsayCBS manages backups and recovery. When those backups support restoration of patient services, information accessible to the backup server is part of the recovery dependency. The backup-service owner should verify the replacement hotfix and investigate suspected compromise separately.
Affected: The command-injection flaw, which permits commands to run on the server, affects the v7/v8/v9/v10 installations covered by Ahsay’s correction. It can be combined with the authentication-bypass flaw CVE-2026-105133.
Response: Use replacement hotfix 10.3.4.45 for affected v10, or 9.15.2.70 for affected v7/v8/v9, then reboot as directed. The linked partner download requires an existing login.
Severity: Numeric CVSS not established in the retained vendor evidence.
Release history: Replacement-fix correction 2026-10-12; exact original release dates not established.
Exploitation status: Known exploited — CISA KEV. Added 2026-10-14; CISA remediate-by: 2026-10-17.
Dates: Disclosure: Not established. Last material update: 2026-10-14. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
Cisco Secure Email Gateway — CVE-2026-76519
Details
Cisco Secure Email Gateway filters incoming email before delivery to users. A provider may route referrals and other clinical or administrative correspondence through it. The email-security owner should identify the enabled inspection features and scanner version, as well as the appliance’s operating software.
Affected: Physical or virtual Secure Email Gateway running vulnerable AsyncOS operating software, with AMP File Reputation enabled and assigned to a mail policy, and Content Scanner Tools below 25.3.0.5525. AMP File Reputation checks file reputation as part of email inspection. A crafted email attachment can lead to commands running with root privileges, the appliance’s highest level of control.
Response: Upgrade to AsyncOS 15.5.5-014 or 16.5.0-780; AsyncOS 16.0 installations must move to a supported fixed release. On licensed supported releases, Content Scanner Tools 25.3.0.5525 or later also fixes the issue without restarting the operating system. Verify installed versions. Preserve forensic evidence before remediation where compromise is suspected. If at least one cluster appliance is compromised, Cisco recommends restoring every member to a secure configuration because the private SSH keys used between members may have been stolen. Contact Cisco support (TAC) for suspected physical-appliance compromise or when restoration cannot be completed.
Severity: CVSS 3.1: 9.8 (Cisco).
Release history: Vendor fix advisory 2026-10-14; exact per-build release dates not established.
Exploitation status: Known exploited — CISA KEV. Added 2026-10-14; CISA remediate-by: 2026-10-17.
Dates: Disclosure: 2026-10-14. Last material update: 2026-10-14. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
Cisco affected features, fixes and recovery guidance · CISA record
Microsoft Outlook email for Windows — CVE-2026-70242
Details
Outlook is email software that care-coordination or administrative teams may use for referrals and other sensitive correspondence. The endpoint or Office deployment owner should identify the Windows product, update channel and running build.
Affected: A remote-code-execution flaw, which can let an attacker run code on the computer, affects Microsoft 365 Apps for Enterprise and Office Long Term Servicing Channel (LTSC) 2021/2024 on Windows, 32-bit or 64-bit (x64). Mac applicability is not established for this identity. A compromised workstation could expose information its user can access.
Response: 2026-10-13 security baselines include LTSC 2021 build 14334.20974, LTSC 2024 build 17932.21056 and Microsoft 365 Current Channel 2609 build 20430.20182. Monthly/Semi-Annual Enterprise channels use their own entries in Microsoft’s table. Install an applicable fixed or later security build and verify the running version.
Severity: CVSS 3.1: 9.8 (Microsoft CVE authority).
Release history: 2026-10-13 Office security releases.
Exploitation status: Not listed in CISA KEV at the 2026-10-26 check; no CISA remediate-by: date listed.
Dates: Disclosure: 2026-10-13. Last material update: 2026-10-13. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
Microsoft Office security updates by product/channel · Microsoft CVE record
Microsoft Outlook email for Windows and Mac — CVE-2026-70291
Details
Outlook provides email on both Windows and Mac computers. Teams exchanging clinical or administrative correspondence may use both platforms. The endpoint or Office deployment owner should check each platform separately; a Windows update report alone does not confirm that the Mac applications are fixed.
Affected: A remote-code-execution flaw, which can let an attacker run code on the computer, affects the listed Windows Microsoft 365/Office Long Term Servicing Channel (LTSC) products and Office for Mac, including supported subscription and LTSC editions.
Response: Use the 2026-10-13 Office product/channel security table for Windows. Install 16.114 build 26101123 or later on Mac. Verify the installed application build; the Windows build numbers are not Mac fixes.
Severity: CVSS 3.1: 9.8 (Microsoft CVE authority).
Release history: Windows security releases 2026-10-13; Mac 16.114 security release 2026-10-14.
Exploitation status: Not listed in CISA KEV at the 2026-10-26 check; no CISA remediate-by: date listed.
Dates: Disclosure: 2026-10-13. Last material update: 2026-10-14. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
Microsoft Office security updates · Office for Mac security release · Microsoft CVE record
Windows security controls and Outlook.com — CVE-2026-96951
Details
Windows supports clinical workstations and servers, and its Shell supplies parts of the user interface. Outlook.com is Microsoft’s hosted email service. The endpoint or server owner should identify the installed Windows edition and servicing path; a change to Microsoft’s hosted email service does not update a provider’s Windows machines.
Affected: The flaw can bypass a security protection on the listed Windows client/server products and Outlook.com. Applicability depends on product edition, processor architecture and whether Windows Server uses the Server Core installation option.
Response: Use Microsoft’s Security Update Guide to identify the applicable security update for the installed product and follow its deployment instructions. Do not treat version numbers that mark the end of an affected range in the CVE record as a verified Microsoft Knowledge Base (KB) update number or a version to install.
Severity: CVSS 3.1: 8.8 (Microsoft CVE authority).
Release history: Exact applicable KB/build and fix-release date remain product-specific and are not established in this record.
Exploitation status: Known exploited — CISA KEV. Added 2026-10-13; CISA remediate-by: 2026-10-16.
Dates: Disclosure: 2026-10-13. Last material update: 2026-10-16. First documented CCD tracking: 2026-10-19. First newsletter appearance: not established. CCD display until: 2026-11-02.
Microsoft Security Update Guide · Microsoft CVE record · CISA record
The usual display interval is 14 calendar days from documented first CCD tracking; bounded decisions identify unknown earlier history. Leaving the active list does not mean a vulnerability is resolved. CISA remediate-by dates are shown separately. Known exploited — CISA KEV identifies a vulnerability in CISA’s Known Exploited Vulnerabilities catalog: CISA has evidence that attackers have exploited it. CVSS is a severity score; a proof-of-concept is a research demonstration. These are different from observed exploitation. Neither a KEV listing nor a score establishes that every installation or a healthcare organization was compromised.
Sources
The reporting window ends October 26 at 04:00 UTC. Primary status checks for the lead stories occurred at 03:51–03:54 UTC. BeyondTrust and Cisco recovery instructions were rechecked after the cutoff to verify earlier reporting. The PAN-OS patch-status update was checked October 26 at 09:43 UTC and is dated separately in the PHP priority item. The SafePay advisory was published October 20; its primary text was checked October 26 at 12:05 UTC. The supplier-certificate brief uses the October 21 Go advisory, checked October 26 at 12:10 UTC. The GlobalProtect campaign brief uses an October 19 update checked October 26 at 12:53 UTC. Parkview’s undated restoration banner was checked October 26 at 12:57 UTC; its availability at the reporting cutoff is unknown. Continuing records retain their dated evidence; later verification is not a new in-window event. Source and event dates appear beside the relevant records.
Primary sources and attributed reporting
- PAN-OS affected and fixed versions
- PHP announcements and version guidance
- OpenEMR image follow-ups
- Unit 42’s corrected brief
- Arista’s advisory and fixed branches
- Collabora’s applicability and remedy
- Unit 42 campaign update, October 19 at 23:00 UTC
- Vendor exposure conditions and fixed-version matrix
- CISA KEV record
- Quest’s Quanum notice
- October 22 filing
- Cleveland19’s report carrying UH’s statement
- UH service information
- Parkview’s current service statement
- Parkview MyChart and current banner
- October 19 report of the earlier shutdown
- Joint advisory AA26-293A, official FBI/IC3 copy
- Mozilla incident record
- Go advisory GO-2026-6809 / CVE-2026-111943, published October 21
- BASS’s notice
- Corrected attack chain
- Affected downloads and recovery guidance
- Original incident report and startup warning
- Anthropic’s report
- Health examples and limits, pages 15–17
- Q3 briefing
- Public slides
- FDA final guidance
- October 21 availability notice
- FDA priorities and comment instructions
- Regulations.gov docket FDA-2012-N-1021
- FDA draft and submission instructions
- Regulations.gov docket FDA-2026-N-9505
- FDA workshop, registration link and materials
- OIRA CIRCIA review status
- Unified Agenda planning entry
- HHS proposal and current-rule statement
- FDA Lumify scope and use instructions
- FDA recall record Z-0152-2027
- FDA StatStrip models and mitigation instructions
- Nova customer correction notice
- FDA individual recall record
- FDA VentStar affected hoses and inspection instructions
- FDA event 99787
- FDA Medline whole-kit removal instructions
- FDA full affected-kit and lot workbook
- FDA event 99669
- FDA AVID kit scope and whole-kit removal instructions
- FDA event 99672
- PHP advisory, affected versions and CVSS
- PHP state-reset advisory and fixes
- CISA KEV record CVE-2026-114625
- Earlier public report and maintainer response
- Nextcloud app releases
- CISA KEV record CVE-2026-110447
- Fortinet CVE record and solutions
- Fortinet advisory
- FortiProxy 7.4.12 release notes
- CISA KEV record CVE-2025-61624
- Palo Alto Networks scope and fixes
- PAN-OS full affected/fixed maintenance table
- CISA KEV record CVE-2026-0322
- BeyondTrust Remote Support advisory
- 2026-10-16 incident update and PRA precaution
- CISA KEV record CVE-2026-102764
- Ivanti October release guidance
- Ivanti CVE record
- Ivanti detailed advisory
- CISA KEV record CVE-2026-104935
- Ahsay replacement-fix notice
- CISA KEV record CVE-2026-105133
- CISA KEV record CVE-2026-105134
- Cisco affected features, fixes and recovery guidance
- CISA KEV record CVE-2026-76519
- Microsoft Office security updates by product/channel
- Microsoft CVE record
- Office for Mac security release
- Microsoft CVE record
- Microsoft Security Update Guide
- Microsoft CVE record
- CISA KEV record CVE-2026-96951