The November 12 update covers Siemens engineering software and gateways, France’s attribution of the October refrigeration attacks, and the U.S. electricity outlook. The November 9 reporting and opinion follow.
November 12, 2026 update · Includes the November 9 edition
On November 10, Siemens published SSA-979641 / CVE-2026-59082 for SIMATIC WinCC Graphics Designer. Opening a malicious file can execute code on the engineering device. Siemens lists WinCC V7.5, V8.0 and V8.1 as affected, with fixes unavailable for those versions at publication. Its mitigation includes opening files only from trusted sources. The advisory describes a vulnerability requiring user interaction. Siemens reported the vulnerability and its prerequisites. Siemens ProductCERT · SSA-979641
Operational analysis. An engineering workstation receives files from contractors, backups and earlier projects. Those transfers deserve explicit ownership because compromising that workstation could affect its engineering credentials and accessible systems. The consequences depend on its privileges and network connections. Siemens ProductCERT · SSA-979641
Critical Manufacturing extract. Include contractor-supplied HMI files in the engineering change process. Record their origin, review responsibility and the workstation authorized to open them. Siemens ProductCERT · SSA-979641
Water and Wastewater extract. Where WinCC is installed, coordinate engineering-workstation changes with operators and verify that required monitoring and alarm workflows still function afterward. Siemens ProductCERT · SSA-979641
What to check: Confirm installed versions, identify who accepts external project files and follow Siemens’ mitigation guidance. Review suspicious files in an appropriately isolated engineering environment. Plan any software migration with compatibility checks, a verified backup and a documented recovery procedure.
The November 10 revision of SSA-834709 adds an affected configuration to an existing Node-RED advisory. Siemens identifies missing authentication that can allow an unauthenticated attacker to create flows and execute commands with maximum privileges. Its product table distinguishes Industrial OS installations, for which specified releases can be updated to V4.3.4-1 or later, from listed Example Image configurations with Node-RED, for which no fix is currently available. This configuration expansion is the material update to the gateway topic covered previously. Siemens ProductCERT · SSA-834709
Operational analysis. A hardware model alone is insufficient for deciding whether a gateway has been remediated. The installed image and applications determine which advisory instructions apply. Gateways can also connect operational data to other systems, making their actual communication paths important to the response. Siemens ProductCERT · SSA-834709
Information Technology extract. Extend the gateway inventory to include its software image and application configuration. Assign responsibility for maintaining those details alongside network access rules. Siemens ProductCERT · SSA-834709
Controls Engineering extract. During commissioning, record the installed image and management-access configuration so future maintainers can determine advisory applicability. Siemens ProductCERT · SSA-834709
What to check: Record the exact order number, operating-system image, version and Node-RED installation status. Match that combination to the vendor table and mitigation instructions. Validate required data flows after an approved change.
On November 9, France’s foreign ministry attributed the October 11–12 attacks against supermarket refrigeration controllers to the Iranian SHAHID KAVEH cyber unit, which it links to the Islamic Revolutionary Guard Corps. The ministry says the campaign targeted equipment deployed across more than 700 French retail sites and caused equipment damage, fires and substantial food losses. These are the French government’s findings. The new development is formal attribution and its stated impact assessment, updating the earlier roundup’s unresolved attribution. The statement does not establish that every refrigeration incident elsewhere in Europe belonged to this campaign. French Ministry for Europe and Foreign Affairs · November 9
Operational analysis. Refrigeration security connects remote access, equipment protection, stock preservation and incident response. An alarm helps only if someone receives it and can act while the primary monitoring system is unavailable or untrusted. French Ministry for Europe and Foreign Affairs · November 9
Food and Agriculture extract. Document how temperature-sensitive stock would be protected during a controls incident, including independent readings and escalation ownership. French Ministry for Europe and Foreign Affairs · November 9
Commercial Facilities extract. Review the contractor’s remote-access path and the building operator’s ability to detect and respond to abnormal refrigeration behavior. French Ministry for Europe and Foreign Affairs · November 9
What to check: Run a tabletop exercise covering an unauthorized setpoint change. Identify who can restrict remote access, verify actual temperature independently and authorize product-preservation measures.
The U.S. Energy Information Administration released its November Short-Term Energy Outlook on November 10, using a forecast completed November 5. It expects continued electricity-generation growth through 2027, with increasing commercial and industrial demand and expanding renewable generation. Weather assumptions influence the forecast. These national projections require local utility and site data before being used for a particular facility decision. EIA · November 2026 Short-Term Energy Outlook
Operational analysis. For controls projects, the useful questions concern the facility’s actual load profile, capacity constraints and required operating continuity. National growth forecasts provide context for those discussions. EIA · November 2026 Short-Term Energy Outlook
Energy extract. Use the updated forecast as planning context, then document local capacity and operating constraints before specifying control-system changes. EIA · November 2026 Short-Term Energy Outlook
What to check: Compare planned equipment additions with interval-meter data and the utility’s service-capacity information. Establish a measured baseline before proposing load-management controls.
Carrollton’s engineering page links to the city’s bid advertisements. The water-treatment SCADA and filter-controls package was unavailable for review. The reported November 17 meeting and December 3 deadline remain unverified, along with eligibility, attendance, amendments and submission requirements. City of Carrollton · Engineering and bid advertisements
The previously listed November 6 date for Asheville SCADA support has passed. The city’s purchasing page returned HTTP 403 during review. Extension, evaluation and award status remain unresolved. City of Asheville · Purchasing bids
What to check: Obtain the current official solicitation and amendments before relying on a meeting date, deadline or eligibility requirement.
Canada’s Cyber Centre reported November 6 that SonicWall vulnerability CVE-2026-19868 was being exploited and had entered CISA’s Known Exploited Vulnerabilities catalog. Its bulletin identifies SonicOS releases before 7.3.4-7013 and 8.2.2-8015. Administrators should check the vendor’s product-specific guidance before selecting an update. Canadian Cyber Centre · November 6, 2026
Operational analysis: For infrastructure operators, an affected firewall may support remote-site communications or authorized vendor access. That dependency makes remediation an operational planning task as well as a security task. These implications depend on the actual deployment. The advisory does not establish compromise at any particular utility or industrial facility. Canadian Cyber Centre · November 6, 2026
What to check: Inventory relevant appliances, confirm applicability and identify the services each device supports. Coordinate remediation with the operational owner, establish recovery arrangements and test required connectivity afterward. Follow vendor guidance when evaluating possible compromise.
Johnson Controls’ November 5 advisory identifies C•CURE 9000 / victor and CVE-2026-106019. The vendor-authored CVE record, published November 6, describes sensitive information being written into logs, potentially enabling use of operating-system credentials. Its affected-product entry lists version 3.20, but does not provide the detailed installer-build scope or remediation procedure. Johnson Controls advisory index · Vendor-authored CVE record · November 6, 2026
Operational analysis: Physical security may operate the application, IT may administer its Windows environment, and an integrator may maintain it. Reviewing the issue requires someone who can connect those responsibilities. The CVE record does not establish active exploitation. Exact affected builds and vendor-prescribed remediation should be confirmed from the full advisory, which could not be retrieved for this edition. Johnson Controls advisory index · Vendor-authored CVE record · November 6, 2026
What to check: Confirm installations and obtain the full vendor advisory. Have the application owner, IT administrator and maintainer establish applicability and the response required. If credential changes are warranted, identify dependent services and agree on functional checks before making them.
A system that controls a pump, a treatment process or a building’s security should not be directly reachable by anyone on the internet. AI-assisted vulnerability discovery makes that position more urgent. In March, Mozilla reported that its collaboration with Anthropic produced 22 CVEs, including 14 high-severity bugs, in an extensively tested browser. Engineers validated the findings and shipped fixes. This is concrete evidence that AI can uncover consequential weaknesses even in software that already receives substantial security scrutiny. Mozilla · March 6, 2026
AI is revealing existing defects in these cases. A CVE is a record of a vulnerability, and a rising count does not translate directly into an equal rise in attacks. Google Threat Intelligence Group’s September analysis found substantial growth in disclosures and observed exploitation, while warning that assignment practices and vendor disclosure cycles complicate interpretation of the totals. My conclusion is that critical infrastructure owners should plan for more weaknesses becoming discoverable. They should reduce the number of paths through which those weaknesses can affect operations. Google Threat Intelligence Group · September 30, 2026
A faster discovery cycle meets a slower maintenance cycle. An operational system’s maintenance window depends on more than an available patch. Someone must understand process dependencies, coordinate the work, establish recovery arrangements and verify that the equipment still performs its function. My concern is the mismatch between those requirements and increasingly capable software analysis. An exposed system remains reachable while its owner works through the engineering decision. Removing unnecessary exposure buys defenders room to make that decision properly. Mozilla · March 6, 2026
The recommendation already has an operational basis. In July, CISA urged owners and integrators to remove publicly exposed PLCs and other OT from the internet after observing attacks that changed passwords and IP addresses. The agency reported boil-water notices and sustained manual operations. Its warning also highlighted cellular modems that might be missing from network inventories. CISA · July 30, 2026
Remote access needs an engineered boundary. For critical controls, direct public access should be an exception requiring a compelling justification and explicit ownership. Necessary remote support should pass through a maintained security boundary, with access limited to the people, systems and time required. The UK’s National Cyber Security Centre recommends brokered connections through a secure gateway in a separate controlled segment, reduced exposure time and active maintenance of the intermediary itself. NCSC · Limit the exposure of your connectivity
A gateway still needs patching. Segmentation still needs verification. Removing direct exposure does not eliminate compromised laptops, malicious insiders or other routes into the environment. It reduces one substantial avenue of attack. Changes also need operational planning. Before removing a connection, establish what depends on it, how operators will retain visibility and control, and how required service will be tested afterward. NCSC · Limit the exposure of your connectivity
Make connectivity earn its place. The question for leadership is straightforward: Which critical systems can outsiders reach, why is that access necessary, and who is accountable for it? Answer it jointly across IT, operations, engineering and vendors. Include forgotten modems, temporary support connections and administrative interfaces. AI-assisted discovery can help defenders fix software faster. Infrastructure owners should use that advantage while reducing their dependence on every exposed component remaining secure. Critical systems deserve a deliberate connectivity design. Public reachability should never be the accidental default. CISA · July 30, 2026 · NCSC · Limit the exposure of your connectivity
What to check: Identify direct public exposure and undocumented remote-access paths with the operational owner. Plan removal or mediation of unnecessary exposure, preserve required visibility and control, and verify normal service after the change. This column expresses editorial judgment; its historical examples are context, not newly reported November incidents.
The question for this week: Which critical systems can outsiders reach, why is that access necessary, and who is accountable for it?
Coverage note: Two selected developments from November 5–9, followed by a clearly labeled opinion column using historical sources. This edition does not represent comprehensive coverage of all 16 critical infrastructure sectors. Detailed Johnson Controls installer-build scope and remediation remain subject to the full vendor advisory. Unverified Government Watch leads are excluded. The November 12 update adds reporting on November 9–12 and a Government Watch note on what remains unverified.