CVE-2026-4827: Schneider Electric Easergy MiCOM C264 · Insufficient Entropy
Affects Schneider Electric Easergy MiCOM C264Source CVE Database V5
Not known to be exploited · CVSS 8.7 High.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Schneider ElectricEasergy MiCOM C264 | Affected
| Fixed in– |
| Schneider ElectricEasergy C5 | Affected
| Fixed in– |
| Schneider ElectricEasergy MiCOM P30 | Affected
| Fixed in– |
| Schneider ElectricEasergy MiCOM P40 | Affected
| Fixed in– |
| Schneider ElectricEcoStruxure™ Power Automation System Gateway (EPAS-GTW) | Affected
| Fixed in– |
| Schneider ElectricEcoStruxure™ Power Automation System User Interface (EPAS-UI) | Affected
| Fixed in– |
AI-suggested
Until a patch is available, consider limiting network exposure of affected devices and applying compensating controls as appropriate.
Description
We strongly recommend the following industry cybersecurity best practices. * Locate control and safety system networks and remote devices behind firewalls and isolate them from the business network. * Install physical controls so no unauthorized personnel can access your industrial control and safety systems, components, peripheral equipment, and networks. * Place all controllers in locked cabinets and never leave them in the “Program” mode. * Never connect programming software to any network other than the network intended for that device. * Scan all methods of mobile data exchange with the isolated network such as CDs, USB drives, etc. before use in the terminals or any node connected to these networks. * Never allow mobile devices that have connected to any other network besides the intended network to connect to the safety or control networks without proper sanitation. * Minimize network exposure for all control system devices and systems and ensure that they are not accessible from the Internet. * When remote access is required, use secure methods, such as Virtual Private Networks (VPNs). Recognize that VPNs may have vulnerabilities and should be updated to the most current version available. Also, understand that VPNs are only as secure as the connected devices. For more information refer to the Schneider Electric [Recommended Cybersecurity Best Practices](https://www.se.com/us/en/download/document/7EN52-0390/) document.