XWEB EVO CVE-2026-124002: Check the 5.7.0 boundary and restrict access
CVE-2026-124002 allows an unauthenticated remote attacker to execute operating-system commands on affected Copeland XWEB EVO refrigeration supervisors. The flaw is in username processing before password verification. VulnCheck’s advisory describes how the issue can combine with a privileged interpreter to reach root access. The CNA rates it Critical: CVSS 4.0 9.3, CVSS 3.1 9.8.
The vulnerability was disclosed on November 12, 2026. VulnCheck’s November 13 research post provides follow-up analysis of that disclosure.
Check the issue-specific version range
The CNA record lists 5.2.3 up to, but excluding, 5.7.0 as affected. It explicitly marks 5.7.0 unaffected for this issue. Version 5.6.2 is still inside the affected range.
Record the model and running firmware from existing maintenance records or the supplier-approved administration procedure. Retain the full build string, even if an inventory comparison uses only its numeric version. Do not infer the running version from a downloaded update file.
An unaffected result for this CVE does not establish overall XWEB EVO safety. Other credential vulnerabilities in VulnCheck’s research extend through 5.8.8. Copeland’s lifecycle bulletin ended firmware maintenance and security patches for the entire EVO family on March 16, 2026.
Make an offline inventory check
This Python 3 helper compares a manually entered numeric version with the CNA range. It makes no network requests and cannot identify a device or confirm its firmware. A suffix or unknown version needs manual review; do not discard build information to force a result.
Create a scratch directory on Linux:
workdir=$(mktemp -d) && cd "$workdir"Stop if setup fails. Keep the following steps in the same shell. Save this file as xweb_124002_inventory.py:
import argparse
import re
parser = argparse.ArgumentParser(allow_abbrev=False)
parser.add_argument("version", help="numeric XWEB EVO version from your inventory")
args = parser.parse_args()
if not re.fullmatch(r"(0|[1-9][0-9]{0,3})(\.(0|[1-9][0-9]{0,3})){2}", args.version):
parser.error("use three numeric components, for example 5.6.2; no suffix")
version = tuple(map(int, args.version.split(".")))
print(f"Inventory version: {args.version}")
if (5, 2, 3) <= version < (5, 7, 0):
print("CVE-2026-124002: inside the CNA affected range.")
elif version == (5, 7, 0):
print("CVE-2026-124002: explicitly unaffected in the CNA record.")
else:
print("CVE-2026-124002: outside the listed range; confirm applicability with supplier.")
print("Offline comparison only; no overall XWEB EVO safety verdict.")Run these synthetic inventory examples:
python3 xweb_124002_inventory.py 5.6.2
python3 xweb_124002_inventory.py 5.7.0Actual output captured on Debian 13 with Python 3.12.14 on November 13, 2026. Both commands exited 0:
Inventory version: 5.6.2
CVE-2026-124002: inside the CNA affected range.
Offline comparison only; no overall XWEB EVO safety verdict.
Inventory version: 5.7.0
CVE-2026-124002: explicitly unaffected in the CNA record.
Offline comparison only; no overall XWEB EVO safety verdict.The helper rejects missing arguments, malformed versions and build suffixes with exit status 2 and no comparison. It directs versions outside the listed range to supplier review. Remove the scratch files after use:
rm -- xweb_124002_inventory.py
cd /
rmdir -- "$workdir"
unset workdirRestrict exposure and plan migration
Coordinate changes with refrigeration operations and the supplier. Do not abruptly disconnect controllers or interrupt temperature monitoring. The lifecycle bulletin recommends inventory, network segmentation, restricted access and enhanced monitoring while planning a move to XWEB PRO.
- Remove public management exposure through approved firewall or routing changes. Limit administration to authorized management hosts through a controlled access path; preserve required monitoring and alarm traffic.
- Have the supplier confirm the appropriate replacement model, supported firmware and migration sequence. The recommendation to move to PRO does not establish that every PRO release is safe. Do not treat an archived EVO update as a supported long-term remedy.
- Before a maintenance window, agree on configuration backups, recovery access and a rollback plan. After each change, check normal operator access, temperature reporting and alarm delivery with the operations team. Review access rules and logs to confirm the intended management restrictions.
These measures reduce exposure; they do not prove that an appliance is uncompromised. If there are signs of unauthorized changes, preserve available logs and involve the incident-response team and supplier before rebuilding or restoring service. Only the offline inventory helper was tested here. No appliance, firmware update or exploit was tested.
Acknowledgements
This post was created with assistance from AI.