The systems keeping your food cold can be taken over without a password.

Dutch consultancy Midnight Blue published six flaws in Danfoss AK-SM800A refrigeration controllers this week, and the findings should rearrange how you budget plant cybersecurity.

There is no patch.

Firmware 5.4.0, the newest release, still allows remote takeover with no login. Cyber agencies in Belgium, Ireland, and Germany told operators this week to treat the boxes as live exposure, not a waiting vendor ticket.

This is a bad look for any OEM still shipping management interfaces that trust the network.

You already run a firewall, a brute-force dashboard, and a threat-protection stack aimed at laptops and VPN users. The cooler never sat in that picture. It lives on a plant VLAN someone bridged for a vendor, or behind a cellular modem a contractor labeled temporary in 2019.

Unpatched Danfoss refrigeration controller flaws allowing remote takeover without login
Danfoss AK-SM800A controllers ship with six unpatched flaws that need no login.

Cold rooms hold pharmaceuticals, grocery inventory, and the margin on a food plant. If an attacker can flip setpoints, silence alarms, or brick a controller, you have a product-safety incident wearing an IT badge.

Setpoints, defrost cycles, and alarm relays are the production controls. An attacker who can write those without authenticating does not need ransomware. Spoiled stock and a silent alarm get you the same outage, with a nicer press statement about equipment issues.

Unauthenticated Cybersecurity Leaves the Floor Open

The same pattern showed up on internet-facing software this weekend.

SANS Internet Storm Center honeypots started logging requests for /mcp-rest/test/tools/list. Those probes track CVE-2026-42271 and CVE-2026-48710 in LiteLLM and Starlette. Horizon3.ai showed how the pair chains into remote code execution with no authentication. Scanners did not wait for your change window.

You cannot brute-force a service that never asked for a password.

Threat detection that watches failed logins will stay quiet. Incident response playbooks that start at reset the account have nowhere to start.

Luxury hotels ran into a cousin of this failure. Attackers sent a fake booking request, landed in a reservations inbox, copied genuine refund traffic, and got fraudulent refunds approved. Bruce Schneier called out the usable-security bind: answering strangers is the job, and a guest-first culture punishes hesitation. Owner, operator, and brand each assume someone else owns cyber security. Staff take the blame because they are the only people still in the room.

Your refrigeration vendor map looks a lot like that hotel org chart. Facilities owns the hardware. IT owns the network. The OEM owns the firmware. Procurement owns the support contract. Nobody owns the login that does not exist.

Pull Controllers Off the Public Internet

Security hardening for these boxes is not a dashboard click. Do the inventory work your CMDB skipped.

  • Immediate: dump every Danfoss AK-SM800A and sibling controller from the CMDB, BACnet lists, and the dusty vendor remote-access spreadsheet. If you cannot name the firmware, treat it as 5.4.0 or older.
  • Immediate: remove public routing. No inbound NAT, no vendor VPN that hairpins onto the plant LAN, no cellular modem with a public IP. Management goes through a jump host you control.
  • Immediate: search proxy, WAF, and MCP logs for /mcp-rest/test/tools/list and other unauthenticated tool-list calls. Isolate those listeners the same day.
  • Ongoing: put OT management on a dedicated VLAN with default-deny at the firewall. Defense in depth here means the controller cannot start unexpected WAN sessions, and the WAN cannot start anything toward the controller.
  • Ongoing: put an authenticating proxy in front of every web UI, including temporary vendor portals. If the product cannot do auth, the network has to.
  • Ongoing: add cold-chain fail-safes to incident response. Who can freeze setpoints locally if the controller is hostile. Who calls the food-safety officer. What evidence you pull before you yank power.

Skip the theatrical tabletop until those six items have owners and dates.

Split Ownership Hides the Outage

You will be tempted to buy another OT scanner and call the week closed. Scanners are fine. They do not patch a vendor that has not shipped a fix, and they do not assign an owner.

Write the RACI on paper this week. Facilities names the asset. Network engineering names every path that can reach it. Security names the compensating controls until Danfoss ships a build that actually closes the six bugs. Legal names who talks to regulators if a pharmacy fridge drifts.

If that meeting feels theatrical, look at the hotel refund fraud again. Split accountability is how fraudulent refunds get approved and how unauthenticated controllers stay reachable. The convenient story is always a careless user. The operational story is a missing owner.

Weekend scanners already moved.

Plant cybersecurity that only counts laptops will keep missing the asset that spoils a warehouse. Put the cooler on the same untrusted list as any other unauthenticated service, then keep it there until a real patch exists.

Sources

Take Control of Your Server Security

Don't let brute-force attacks slow you down. Try IPBan Pro risk-free for 30 days.

Secure. Automated. Lightweight.

Stay up to date with the latest news, releases and more.

Take Control of Your Server Security

Don't let brute-force attacks slow you down. Try IPBan Pro risk-free for 30 days.

Secure. Automated. Lightweight.