Skip to content
Copeland XWEB EVO CVE-2026-124004: Restrict access and plan migration

Copeland XWEB EVO CVE-2026-124004: Restrict access and plan migration

November 13, 2026

Copeland XWEB EVO versions below 5.6.2 contain an embedded administrator credential that lets an unauthenticated remote attacker gain full administrative access to the application. VulnCheck disclosed CVE-2026-124004 on November 12, 2026. Its CVE Numbering Authority (CNA) record rates the issue Critical: CVSS 4.0 9.3 and CVSS 3.1 9.8. CNA record, VulnCheck disclosure.

Keep the version boundary specific

The CNA lists releases below 5.6.2 as affected and explicitly marks 5.6.2 unaffected for this issue. That does not establish overall safety: a separate administrator-credential flaw covers 5.6.2 through 5.8.8. Do not treat an upgrade to 5.6.2 as remediation for the whole XWEB vulnerability set. Separate credential issue.

Changing the normal administrator password alone is not established remediation for this embedded credential. The issue advisory describes a separate authentication route; it does not establish a password-rotation workaround.

Copeland ended security patches and corrective firmware updates for the entire EVO family on March 16, 2026. Its end-of-support bulletin recommends migration to XWEB PRO, with interim segmentation, restricted access and monitoring. Ask the supplier to confirm the replacement model, supported software and migration procedure. The recommendation does not establish that every PRO release is safe.

Inventory without testing the appliance

Record each installation’s model and running firmware from authorized maintenance records, with the owner and management-network access rules. Resolve missing or stale version information through the responsible operator. Do not try the embedded credential to check exposure.

This Linux helper compares a manually recorded version with this CVE’s boundary. It makes no network connection and cannot validate the inventory or determine whether a release exists.

With Python 3 installed, create a scratch directory:

workdir=$(mktemp -d) && cd "$workdir"

Stop if setup fails. Keep the remaining commands in the same shell. Save as xweb_124004_inventory.py:

import argparse
import re

parser = argparse.ArgumentParser(allow_abbrev=False)
parser.add_argument("--version", required=True)
args = parser.parse_args()
if not re.fullmatch(r"[0-9]{1,3}\.[0-9]{1,3}\.[0-9]{1,3}", args.version):
    parser.error("enter a recorded numeric version such as 5.6.1; no suffix")
version = tuple(map(int, args.version.split(".")))
if version < (5, 6, 2):
    result = "in the CNA affected range"
elif version == (5, 6, 2):
    result = "explicitly unaffected for this CVE only"
else:
    result = "outside this CVE's recorded affected range"
print(f"CVE-2026-124004 / {args.version}: {result}.")
print("Offline comparison only; EVO remains unsupported and other flaws apply.")

Run these synthetic inventory examples:

python3 xweb_124004_inventory.py --version 5.6.1
python3 xweb_124004_inventory.py --version 5.6.2

Actual output on Debian 13, Python 3.12.14, November 13, 2026; both commands exited 0:

CVE-2026-124004 / 5.6.1: in the CNA affected range.
Offline comparison only; EVO remains unsupported and other flaws apply.
CVE-2026-124004 / 5.6.2: explicitly unaffected for this CVE only.
Offline comparison only; EVO remains unsupported and other flaws apply.

Missing arguments, unknown, incomplete versions and suffixes such as 5.6.2-beta fail with exit status 2 and no classification. Remove only the scratch file and directory:

rm -- xweb_124004_inventory.py
cd /
rmdir -- "$workdir"
unset workdir

Restrict access while planning replacement

Coordinate changes with refrigeration operations and the supplier. Remove public management exposure and permit administration only through an approved, restricted access path. Separate management traffic from unrelated networks while preserving required controller communication and alarm delivery. Do not abruptly disconnect or reboot equipment that supports the cold chain.

Agree on a maintenance window, configuration backup and recovery plan before any firmware change or migration. Afterward, verify the running version through the approved administration process, review the management access rules, and test temperature monitoring, control functions and alarm delivery with operations staff. Retain the configuration and version evidence in the maintenance record.

Segmentation reduces exposure; it does not prove that an installation is uncompromised. If logs or configuration changes suggest unauthorized access, preserve evidence and involve the incident-response team and supplier before recovery. Only the offline helper was tested here. No appliance authentication, exploit or firmware update was tested.

Acknowledgements

This post was created with assistance from AI.

Last updated on