Early warning
Threat actors exploiting two new flaws in Copeland XWEB EVO, with no patches
Per a VulnCheck blog post relayed by Catalin Cimpanu, threat actors are exploiting two newly disclosed vulnerabilities in Copeland XWEB EVO refrigeration systems. Copeland retired the product in March, so no patches are available.
Written by a model from the sources below. Verify against them.
- Kind
- Pending CVE
- Vendor
- Copeland
- Product
- XWEB EVO
- Threat actor
- Shahid Kaveh
- Status
- Confirmed
- First seen
- Confirmed
What to do
Isolate XWEB EVO controllers from the internet and untrusted networks.
Restrict access to the device management interface to known administrative hosts.
Monitor for unexpected connections to XWEB EVO devices.
Plan to replace the retired product, since Copeland has not released fixes.
Move XWEB EVO controllers to a supported platform such as XWEB Pro.
Keep XWEB EVO devices off the public internet and segment them behind a VPN.
Timeline
- Made public by Mastodon
- First seen by cve.now1 day
- Record last updated
- Confirmed as CVE-2026-124014
Evidence 4
- SocialMastodon
“VulnCheck hat 14 Sicherheitslücken im Kühlungsüberwachungssystem Copeland XWEB EVO veröffentlicht.”
- PressCatalin Cimpanu on Bluesky
“Threat actors are exploiting two new vulnerabilities in Copeland XWEB EVO refrigeration systems”
- SocialMastodon
“Copeland XWEB EVO flaw CVE-2026-124010 gives unauthenticated root and is exploited in the wild, alongside CVE-2026-124014.”
- PressSecurityWeek
“Exploitation attempts against a vulnerability in Copeland’s XWEB EVO refrigeration controllers began less than two hours after the issue was made public last week, according to VulnCheck.”
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about SZB-cf7ea4d8d1
Has Copeland confirmed it?
Mastodon, Catalin Cimpanu on Bluesky and Mastodon report an attempted attack. None of the sources says the attackers got in.Source: Mastodon, Catalin Cimpanu on Bluesky, Mastodon, SecurityWeek
What should Copeland and Copeland XWEB EVO users do?
Isolate XWEB EVO controllers from the internet and untrusted networks. Restrict access to the device management interface to known administrative hosts. Monitor for unexpected connections to XWEB EVO devices. Plan to replace the retired product, since Copeland has not released fixes. Move XWEB EVO controllers to a supported platform such as XWEB Pro. Keep XWEB EVO devices off the public internet and segment them behind a VPN.
Does it have a CVE?
Yes. It is tracked as CVE-2026-124014 and CVE-2026-124010.Source: CVE-2026-124014, CVE-2026-124010