This Week in Cyber:  November 12–18, 2026

Ransomware halted smart-meter manufacturing and shipments at Osaki Electric, while CISA disclosed six vulnerabilities in water-sector control software. In New Hampshire, a cyber incident at Monadnock Community Hospital disrupted diagnostics and diverted ambulances. Vermont and Maine reported further public-service disruptions; DHS detailed Iran-linked targeting of critical infrastructure, and Texas announced new Watershed 250 partners.


November 18 | Ransomware Suspends Smart-Meter Manufacturing and Shipments at Osaki Electric

What happened: Osaki Electric disclosed on November 18 that it had confirmed a ransomware attack after discovering encrypted server data the previous morning. It isolated systems from external networks and, as a precaution against further damage, shut down production-related systems at its Saitama facility and related sites operated by Iwate Osaki Electric and Osaki Platech. Production and shipment of smart meters and other products were suspended. Osaki had not determined when manufacturing would resume, and it was investigating whether data had been leaked. It did not report a compromise of deployed smart meters or utility networks. [1]

Why it matters: The documented interruption is at a supplier, not on a power grid. Utility teams managing meter rollouts or replacements should identify dependence on single manufacturers, review spare-device inventories and delivery commitments, and determine which projects can continue if shipments stop. The larger operational risk here is procurement and maintenance continuity; nothing in Osaki's first disclosure establishes manipulation of meters already deployed in the field.


November 18 | Vermont Dispatch Platform and Maine City Systems Remain Offline

What happened: Vermont public-safety agencies continued using backup procedures after the vendor operating the Valcour dispatch and records platform reported a potential security incident. State agencies helped take the system offline as a precaution and said 911 and emergency response were not interrupted, though some records and administrative functions could be slower. [2] In South Portland, Maine, city offices and the library remained closed while investigators examined a suspected cyberattack. Computer and phone services were disrupted, and officials said police, fire and emergency medical services remained operational. Neither event had a publicly established connection to the other. [3]

Why it matters: These incidents distinguish public-facing service disruption from the loss of core emergency response. Municipal and public-safety operators should test whether dispatchers can retrieve records, log calls, and reconcile work after a vendor-hosted platform is taken offline, while city agencies should document offline alternatives for payments, permits, and resident communications. Vermont described a preventive shutdown following a potential vendor incident; South Portland's intrusion details remained under investigation.


November 18 | DHS Testimony Details Iran-Linked Targeting of U.S. Infrastructure

What happened: In written testimony for a November 18 House Homeland Security hearing, DHS Secretary Markwayne Mullin said Iranian government cyber actors and pro-Iran cybercriminals had increasingly targeted transportation, healthcare, water, energy, and financial networks since February 2026. He described past localized, minimally disruptive effects against poorly secured industrial control devices, while warning that vulnerable systems could enable more serious disruption. The testimony presented an assessment of an ongoing threat; it did not identify a new November 18 intrusion or attribute the week's unrelated outages to Iran. [4]

Why it matters: The most actionable detail is the exposure of poorly secured industrial control devices, not the nationality in the headline. Operators should compare their externally reachable controllers, remote administration services, and access controls against current asset records, then eliminate unnecessary public exposure. Any resulting investigation should depend on observed activity and technical evidence. The testimony does not justify attributing the New England disruptions or Osaki's ransomware incident to the same actors.


November 17 | CISA Discloses Six Vulnerabilities in Water-Sector InfoScan Software

What happened: CISA published advisory ICSA-26-321-01 on November 17 covering six vulnerabilities in Dorsett Controls InfoScan versions 1.45.0 and earlier. The weaknesses include certificate-validation failures, hard-coded cryptographic material, missing authentication for a critical function, and information exposure. Depending on the flaw, exploitation could disclose system information, recover credentials, or interfere with application data and communications. Dorsett recommended upgrading to version 1.46 or later and provided a separate update path for offline customers. CISA said it had not received reports of known public exploitation specifically targeting the vulnerabilities. [5]

Why it matters: Water and wastewater operators should first determine whether InfoScan is installed, which version runs, and which management paths can reach it. A patch plan must account for both network-connected and offline deployments, including testing before changes to operational environments. Because CISA has not reported known exploitation of these flaws, the immediate decision is exposure reduction and controlled remediation, not a claim that a water utility has already been compromised.


November 17 | CISA Calls for Immediate Patching of Critical Java4Shell Vulnerability

What happened: CISA warned on November 17 about CVE-2026-114938, dubbed Java4Shell, a critical memory-corruption vulnerability in the Base64 decoder of the x86-64 HotSpot Java Virtual Machine. CISA said specially crafted Base64 input could crash an affected JVM and potentially enable unauthenticated remote code execution. It urged organizations to identify affected Java installations and apply the relevant vendor security updates. This is a software vulnerability alert; the bulletin did not establish a specific compromise of U.S. industrial facilities. [6]

Why it matters: A Java inventory that stops at developer workstations can miss vendor-managed applications and bundled runtimes inside critical business or industrial-support software. Operators should ask suppliers which products embed affected HotSpot components, determine whether those components receive untrusted input, and test patches in representative environments before deployment. The affected Java components and the feasibility of exploitation must be evaluated per installation rather than assumed across every JVM.


November 17 | Texas Names 63 Watershed 250 Partners, Including CrunchAtlas

What happened: Texas Cyber Command announced on November 17 that 63 technology and cybersecurity companies, including CrunchAtlas, had joined Project Watershed 250. The initiative connects Texas water and wastewater utilities with cybersecurity resources supplied at no cost through participating companies. Those resources may include assessments, technical assistance, defensive tools, and remediation support, with utilities choosing services that meet their needs. The announcement identifies participating providers; it does not establish that CrunchAtlas has been assigned a specific utility, begun a deployment, or completed a pilot. [7]

Why it matters: The operational opportunity is a defined route for under-resourced utilities to evaluate help without first procuring a full commercial engagement. Water operators should match offered assistance to their most consequential exposure and response gaps, establish access and data-handling boundaries, and ask what work remains their responsibility after a pilot. Partner participation is not evidence of an installed system, field result, or successful remediation.


November 16 | New Hampshire Hospital Confirms Cyber Incident as Care Disruptions Continue

What happened: On November 16, Monadnock Community Hospital in Peterborough, New Hampshire, confirmed that its continuing server outage resulted from a cyber incident. Investigators were still assessing whether any data had been affected. [8] Its November 18 update said the emergency department remained open but ambulance diversion continued; outpatient radiology and laboratory services, related scheduling, and fax services remained unavailable. Certain elective major surgeries and scheduled radiology and laboratory visits were canceled through November 23. Phone service was restored at most locations, with exceptions at Jaffrey and Antrim offices. The hospital had not announced a full restoration date. [9]

Why it matters: An emergency department can remain open while unavailable scheduling and diagnostic systems still interrupt patient care. Healthcare operators should verify how ambulance diversion is coordinated, where time-sensitive laboratory or imaging work is redirected, and who can invoke downtime procedures across satellite sites. The hospital confirmed a cyber incident but had not established the intrusion method, full scope, or any patient-data exposure.


That's it for this week. We'll be back next Thursday with the next Weekly Roundup.

Sources & References

[1] Osaki Electric Co., Ltd. — Notice Concerning Suspension of Production Due to Ransomware Cyberattack (First Report) ↗ · November 18, 2026

[2] WCAX (quoting Vermont DPS and Agency of Digital Services) — Vermont takes records, dispatch system offline following potential security incident ↗ · November 18, 2026

[3] Portland Press Herald (reporting City of South Portland statements) — South Portland city services remain closed after cyberattack ↗ · November 18, 2026

[4] U.S. House Committee on Homeland Security / DHS — Written testimony of Secretary Markwayne Mullin, Worldwide Threats hearing ↗ · November 18, 2026

[5] CISA — Dorsett Controls InfoScan (ICSA-26-321-01) ↗ · November 17, 2026

[6] CISA — Critical Java Vulnerability Requires Immediate Patching ↗ · November 17, 2026

[7] Texas Cyber Command — 63 Companies Step Up to Defend the Water Systems Texans Depend On in Project Watershed 250 ↗ · November 17, 2026

[8] Monadnock Community Hospital — Server Outage Update | November 16, 2026 (archived hospital notice) ↗ · November 16, 2026

[9] Monadnock Community Hospital — Server Outage Update | November 18, 2026 ↗ · November 18, 2026

Next
Next

This Week in Cyber: November 5 - November 11, 2026