The box that watches over a supermarket's freezer cases is not supposed to be interesting. It sits in a store's back office, logs temperatures, sends alarms when a compressor fails, and lets a refrigeration contractor change setpoints from a browser. This week, it turned into one of the more urgent patching problems in operational technology.
On November 13, VulnCheck published details of 14 vulnerabilities in Copeland's XWEB EVO, a Dixell refrigeration supervisor now sold under Copeland (Emerson). The researchers rebuilt the appliance in a lab from vendor firmware, and every one of the 14 flaws got them to root (uid=0), the account with full control of the device. Two of the flaws are already being exploited in the wild. In one case the attacks started before any public proof-of-concept existed.
The product line reached end of service in March 2026. That has a large effect on what operators can do next.
What XWEB EVO is, and why it matters
XWEB EVO is a supervisory controller. It sits above the individual case and cold-room controllers and gives operators a web interface for monitoring and adjusting them. Whoever controls the supervisor can, in principle, change the temperatures of everything it manages.
This is not a hypothetical worry. According to CyberScoop, XWEB EVO is one of four systems affected in the October hack of refrigeration controllers at about 700 French supermarkets. CyberScoop reports that French authorities have blamed the Iranian government for those attacks; VulnCheck says France attributed the campaign to Iran's IRGC unit Shahid Kaveh. That is the French government's attribution, and neither source ties the two exploitation sources it observed to that campaign.
CyberScoop also reported that XBOW researcher Max Günther set up honeypot servers made to look like a pizza chain's systems. Honeypots are decoy machines that exist to attract attackers and record what they do. Günther's servers were probed within a day, and some of the attempts tried to change temperature settings. Attackers are not only scanning these devices, and at least some attempted to alter temperature settings.
The two flaws under active attack
CVE-2026-124014: unauthenticated config write (CVSS 4.0: 8.8, High). According to its NVD record, XWEB EVO versions 4.3.0 through 5.8.8 let an attacker with no login send a specially crafted request to the device's config.lua endpoint and write arbitrary contents to the system configuration file, /etc/xwebconfig.json. That allows the attacker to tamper with the device's configuration or knock it offline (a denial of service). VulnCheck says it saw 87 exploitation attempts from a single source in the first hour. They began about an hour and forty minutes after the NVD record was published on November 12 at 20:18 UTC. No public proof-of-concept existed at that point. VulnCheck describes the source as an opportunistic scanner acting on a fresh advisory, and no named threat actor is tied to it.
CVE-2026-124010: unauthenticated root command execution (CVSS 4.0: 9.3, Critical). According to NVD, XWEB EVO versions before 5.6.2 include a CGI program, xwconsole.cgi, that runs as root because it is "setuid-root," meaning it always runs with the owner's root privileges no matter who calls it. It passes one request parameter straight to the operating system's shell without cleaning it first. An attacker who can reach the web interface can run commands as root without logging in. VulnCheck says probing for this flaw began at 03:41 UTC on November 13, from a second source that sent four probes that only ran a harmless identity check, with no follow-on payload.
Both CVEs were assigned by VulnCheck acting as a CVE Numbering Authority (CNA). NVD tags them "unsupported-when-assigned," meaning the product was already out of vendor support when the CVE was issued.
The other twelve
VulnCheck's write-up covers the rest of the set. A few stand out because they show how the device was built:
- CVE-2026-124002: command injection through the username field of the
login.lualogin page. Input typed into the login form can end up executed as a command. - CVE-2026-124004: a hardcoded password for an Administrator backdoor account. A hardcoded credential cannot be changed by the owner, and anyone who extracts it from the firmware can use it on every unit running that firmware.
- CVE-2026-124003: a setuid-root
wluainterpreter, a script engine that runs with root privileges. Any local foothold becomes a path to full control. - CVE-2026-124005: a "code of the day" admin password that is derived from the device's MAC address and the current date. Both of those can be predicted or observed, so the password can be calculated.
CyberScoop reports that many of the 14 flaws score between 8 and 9.8 in severity.
Patched or not?
The patch picture is messier than the headlines suggest, so here it is exactly as the sources give it.
- NVD lists CVE-2026-124010 as affecting versions before 5.6.2, so 5.6.2 and later are not affected by that bug.
- NVD lists CVE-2026-124014 as affecting 4.3.0 through 5.8.8. VulnCheck says 5.8.8 is the current firmware and that it is end-of-support. Neither source names a release that fixes CVE-2026-124014.
- VulnCheck says the older, pre-2021
.luabuilds were fixed on the current branch. - CyberScoop reports that patches are available but legacy versions remain exposed. Copeland's advice to CyberScoop was to keep devices off the public internet and update to the latest software.
In short, updating closes some of these holes, including the critical root command injection on older builds. But the latest firmware still falls within NVD's affected range for the config-write bug that is being exploited, and the product line gets no more vendor support. Patching alone does not make these devices safe.
What It Means for Defenders
Who is affected: anyone running Copeland/Dixell XWEB EVO refrigeration supervisors. That includes grocery and convenience chains, restaurant and quick-service operators, cold-storage and food-distribution warehouses, and the refrigeration service contractors who manage these units remotely for clients. If a contractor installed your refrigeration controls, ask them directly whether XWEB EVO is in the stack.
Do these now:
- Get it off the internet. Copeland recommends this. The web interface should not be reachable from the public internet. Put it behind a VPN or a jump host, and limit access to named management addresses. With two flaws exploited without authentication, a device that is still publicly exposed should be treated as compromised until proven otherwise.
- Update to the latest available software. Copeland recommends this too. Versions older than 5.6.2 are open to the critical root command injection (CVE-2026-124010). Units still on pre-2021
.luabuilds should move to the current branch. - Don't treat 5.8.8 as a finished fix. NVD's affected range for the exploited config-write flaw (CVE-2026-124014) runs through 5.8.8, and the product line is end-of-service. Network isolation is the control you can rely on.
- Check for tampering. Review the device configuration and temperature setpoints against known-good values. Look at web logs for unexpected requests to the configuration and console endpoints named above, especially from November 12 onward. Unexplained setpoint changes or alarm configuration changes deserve an incident response.
- Assume credentials are burned. The hardcoded Administrator account and the predictable "code of the day" password mean the device's own login is no protection. Rotate any shared passwords that may have been stored on or used with the unit, including contractor VPN or remote-access credentials.
- Plan a replacement. End-of-service means no vendor fixes for anything found from here on. Budget for migrating to a supported supervisory platform.
- Segment OT from IT. A root shell on a refrigeration controller is also a foothold on whatever network it shares. Keep building and refrigeration controls on their own segment with tightly filtered traffic to corporate systems.
For federal contractors working through CMMC, confirm that any refrigeration or building controls are actually isolated from the systems that handle your regulated data.