If a refrigeration or cold-storage controller of yours reports to a maintenance firm over the internet, by 4G or 5G modem, forwarded port or vendor dial-in, FortiGuard Labs' outbreak alert of 18 November 2026 concerns you. So does the step CERT-FR, Ireland's NCSC, Belgium's CCB and Germany's BSI put first: remove the exposure. Two of them add a condition the alert does not mention. CERT-FR says to check the insurance contract conditions before the data upload to the refrigeration service provider is cut; the CCB says to review contractual and insurance requirements before that reporting stops, and to keep protected remote access so the monitoring continues. The exposure has a contract behind it. Removing it means redesigning how that firm reaches the equipment, not pulling a cable.

If you run Danfoss AK-SM or AK-SC, or Copeland or Dixell XWEB controllers

Ireland's NCSC advisory of 13 November 2026 (read 19 November 2026) covers every product line in the alert. Its steps, in its order. First, under the heading as written, Remove Direct Internet Exposure (only real solution). Second, secure remote access by VPN or equivalent; IP allowlisting is temporary. Third, review setpoints, defrost schedules, alarm settings, remote access permissions and user accounts. Fourth, apply updates and strengthen authentication, which it calls insufficient on their own for an exposed controller. Fifth, isolate end-of-life equipment and assess replacement.

Belgium's CCB advisory of 12 November 2026 (read 19 November 2026) puts removal first, states that "A 4G or 5G modem alone is not a security measure", and has a fourth step headed Contractual Review: "Review contractual and insurance requirements before interrupting data reporting to the refrigeration service provider. Arrange protected remote access so that essential monitoring can continue." CERT-FR's insurance caution sits directly under its first step in CERTFR-2026-ALE-012 (revision of 16 October 2026, read 19 November 2026).

What the alert says, and what it does not

FortiGuard's outbreak alert (18 November 2026, read 19 November 2026) names Danfoss AK-SM and AK-SC, Copeland XWEB and Dixell XWEB, and lists fifteen CVEs with no product mapping. Its timeline runs from about 700 retail sites in France on 11 and 12 October (covered here) through a second wave on 1 and 2 November to the Irish notice of 13 November.

Nobody has established which vulnerability, if any, was used. ICSA-25-140-03 covers three Danfoss AK-SM 8xxA flaws fixed in R4.2 and R4.3.1; ICSA-26-057-10 of 26 February 2026 covers 23 Copeland XWEB PRO flaws, twelve of them in the alert. CISA states in both advisories that no known public exploitation targeting them has been reported to it, and its KEV catalog at version 2026.11.18 holds none of them (KEV feed, read 19 November 2026). CERT-FR names no CVE and does not say how the attackers got in.

France attributed the October attacks to Iran on 9 November 2026, with CERT-FR's CTI report as the evidence, which rests the attribution on converging indications ("un faisceau d'indices"). FortiGuard's Threat Signal says authorities have not linked the November wave to October.

What this means if you run these controllers

Both cautions are worded around the same event: the data reporting to the service provider stops. The maintenance firm's monitoring runs on that feed, in the CCB's wording; CERT-FR's caution implies the insurance conditions may turn on it; the modem may answer to the contractor, not to you. Cut the feed and the monitoring stops; leave it and the controller stays reachable to anyone who finds the address. Danfoss says the AK-SM800A should not be reachable on any software version, Strict Mode included (update guide, read 19 November 2026). The four authorities give the same way out: the firm keeps its access over a VPN or equivalent protected path, and the public address goes away. The contract changes first, the router second.

What to do if you run these controllers

Now

  • The Irish steps above, in order, with the insurance and contract check before the feed stops.
  • Find the exposure with Danfoss's definition (update guide, section 5.1): a public IP, including one from a cellular SIM, forwarded ports, a DMZ host, UPnP or DDNS. Its installer guide (updated 2 November 2026, read 19 November 2026) says remove public-IP exposure from all supervisory units whether or not an incident has been confirmed; a firewall alone is not sufficient.
  • If compromise is suspected, Germany's BSI notice (version 1.1, 17 November 2026, read 19 November 2026) says change all credentials and check connected equipment; CERT-FR's compromised-unit sequence is in our 16 November post.
  • Our recommendation: per unit, write down which firm reaches it, by which path, and whose name is on the modem or line.

This week

  • Patch what has a patch, as maintenance rather than as the step that closes the matter: AK-SM 8xxA to R4.3.1 or later per CISA; XWEB PRO to 1.13 or later per Copeland's February 2026 bulletin (read 19 November 2026). On 19 November Danfoss's download page offered 5.4.0, which its readme says cannot be downgraded, and Copeland's portal offered 1.16.1 of 29 October 2026.
  • Renegotiate the access path against the vendor's design, Danfoss's update guide sections 5.2 to 5.4: default-deny firewall, VPN-only remote access, a dedicated segment isolated from corporate, guest and point-of-sale networks, factory credentials replaced, individual accounts, cellular only with private or NATed SIM addressing and site-initiated VPN tunnels. Our recommendation: its section 5.4 site checklist belongs in the service agreement.

Plan

  • Copeland ended software support for the XWEB EVO family on 16 March 2026 (bulletin, read 19 November 2026): inventory every installation and plan the transition to XWEB PRO.
  • Danfoss's November 2026 cybersecurity requirements (read 19 November 2026) bind every System Manager, the end-of-service AK-SM 800 (2023) and AK-SC355 (2021) included: no direct connection to the public internet, and VPN behind a deny-by-default stateful firewall. Those two lines are what the next service agreement must deliver.

If you cannot patch

Six Danfoss AK-SM800A flaws outside FortiGuard's list have no patch. Midnight Blue's research, reported by the Irish NCSC, the CCB and the BSI, describes pre-authentication remote code execution flaws in firmware up to and including 5.3.2 with no CVE identifiers, and the BSI's 13 November release (read 19 November 2026) cannot rule out that 5.4.0 is affected. The CCB's answer is that removal "must not be delayed while awaiting patches", which leaves the access path, and so the contract, as the control that does not wait on a patch.

Copeland XWEB EVO, a separate family from XWEB PRO, has none either. The BSI reports fourteen flaws published through VulnCheck on 13 November, five of them in the current firmware 5.8.8, and says the five stay unpatched since Copeland ended software support in March 2026; none is among FortiGuard's fifteen or in CISA's KEV catalog, and VulnCheck reports opportunistic probing of two of them. The BSI and Copeland say move to supported hardware; until then Copeland's end-of-support bulletin asks for enhanced monitoring and its best-practices bulletin for restricted inbound and outbound communication and no exposure to the broader internet.

If you are not affected

If every controller passes Danfoss's site checklist and the contractor reaches it only by VPN, the condition those first steps address is absent; the updates and the end-of-life review stay on the list. The six unpatched Danfoss flaws are present through 5.3.2 and the BSI cannot rule out 5.4.0, so what protects a patched unit is the exposure test, not its version number. Record the contract clause that governs the access with the network evidence, and date a recheck: the BSI reports a low three-digit number of such devices still reachable from the internet in Germany, and a modem swap or new service agreement reopens the path on paper before it does on the wire.

If the question is who can reach a controller through a provider's path and what each session changed, that is what our managed OT SOC is for.