HighCVE-2026-4827

    Insufficient Entropy vulnerability on Multiple Products (CVE-2026-4827)

    Published Sources: Schneider Electric, CVE.org, EUVD

    What is affected, what to do

    CWE‑331: Insufficient Entropy vulnerability exists that could lead to unauthorized access when an attacker on the network can exploit weaknesses in session‑management protections.

    The available sources name no fixed version. Check the vendor guidance in the references below.

    Affected
    • Schneider Electric Easergy MiCOM C264 eq Versions D6.x..Versions D6.x
    • Schneider Electric Easergy MiCOM C264 eq Versions D7.33 and prior..Versions D7.33 and prior
    • Schneider Electric Easergy C5 eq Version 1.1.17 and prior..Version 1.1.17 and prior
    • Schneider Electric Easergy MiCOM P30 eq P139 version prior to P139.678.700..P139 version prior to P139.678.700
    • Schneider Electric Easergy MiCOM P30 eq P437 version prior to P437.678.700..P437 version prior to P437.678.700
    • Schneider Electric Easergy MiCOM P30 eq P439 version prior to P439.678.700..P439 version prior to P439.678.700
    • Schneider Electric Easergy MiCOM P30 eq P532 version prior to P532.678.700..P532 version prior to P532.678.700
    • Schneider Electric Easergy MiCOM P30 eq P539 version prior to P539.678.700..P539 version prior to P539.678.700
    • Schneider Electric Easergy MiCOM P30 eq P631 version prior to P631.678.700..P631 version prior to P631.678.700
    • Schneider Electric Easergy MiCOM P30 eq P632 version prior to P632.678.700..P632 version prior to P632.678.700
    • Schneider Electric Easergy MiCOM P30 eq P633 version prior to P633.678.700..P633 version prior to P633.678.700
    • Schneider Electric Easergy MiCOM P30 eq P634 version prior to P634.678.700..P634 version prior to P634.678.700
    • Schneider Electric Easergy MiCOM P30 eq P633 version P633.680.700 only..P633 version P633.680.700 only
    • Schneider Electric Easergy MiCOM P30 eq P634 version P634.680.700 only..P634 version P634.680.700 only
    • Schneider Electric Easergy MiCOM P30 eq P138 version prior to P138.677.700..P138 version prior to P138.677.700
    • Schneider Electric Easergy MiCOM P30 eq P436 version prior to P436.677.701..P436 version prior to P436.677.701
    • Schneider Electric Easergy MiCOM P30 eq P438 version prior to P438.677.701..P438 version prior to P438.677.701
    • Schneider Electric Easergy MiCOM P30 eq P638 version prior to P638.677.700..P638 version prior to P638.677.700
    • Schneider Electric Easergy MiCOM P30 eq C434 version prior to C434.679.700..C434 version prior to C434.679.700
    • Schneider Electric Easergy MiCOM P40 eq Series model numbers with Protocol Option bit as G, H or L and all firmware versions..Series model numbers with Protocol Option bit as G, H or L and all firmware versions
    • Schneider Electric EcoStruxure™ Power Automation System Gateway (EPAS-GTW) eq Version 6.4.616.200.100 and prior..Version 6.4.616.200.100 and prior
    • Schneider Electric EcoStruxure™ Power Automation System User Interface (EPAS-UI) eq Version 3.0.3 and prior..Version 3.0.3 and prior
    • Schneider Electric EcoStruxure™ Power Operation eq Version 2022 CU6 and prior..Version 2022 CU6 and prior
    • Schneider Electric EcoStruxure™ Power Operation eq Version 2024 CU2 and prior..Version 2024 CU2 and prior
    • Schneider Electric iPMFLS eq Version 64.2025.0.13 and prior..Version 64.2025.0.13 and prior
    • Schneider Electric PowerLogic™ P5 Protection Relay eq V02.502.103 and prior..V02.502.103 and prior
    • Schneider Electric PowerLogic™ P7 Protection and Control Platform eq V02.002.002 and prior..V02.002.002 and prior
    • Schneider Electric PowerLogic™ T300 eq Version 2.9.4 and prior..Version 2.9.4 and prior
    • Schneider Electric PowerLogic™ T500 eq Version 11.08.02 and prior..Version 11.08.02 and prior
    • Schneider Electric Saitel DP eq Version 11.06.36 and prior..Version 11.06.36 and prior
    • Schneider Electric EasyLogic T150 (formerly Saitel DR) eq Version 11.06.30 and prior..Version 11.06.30 and prior

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.7

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v4

    8.7

    CVSS v4

    Severity High on the scale from 0 to 10.

    Source: Schneider Electric, CVE.org, EUVD

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 36.0

    Show all metrics
    Severity
    High
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    71.48 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.7 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.7
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    36.0
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-331

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    CWE‑331: Insufficient Entropy vulnerability exists that could lead to unauthorized access when an attacker on the network can exploit weaknesses in session‑management protections.

    Source: schneider_csaf, schneider_advisory, NVD (NIST), CVE.org (MITRE), cvelistv5, ENISA EUVD

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    VendorProductAffected versionsFixed in
    Schneider ElectricEasergy C5
    • Version 1.1.17 and prior
    • 1.1.18
    • —
    • —
    Schneider ElectricEasergy MiCOM C264
    • Versions D6.x
    • Versions D7.33 and prior
    • D7.34
    • —
    • —
    • —
    Schneider ElectricEasergy MiCOM P30
    • P631 version prior to P631.678.700
    • P532 version prior to P532.678.700
    • P638 version prior to P638.677.700
    • P633 version P633.680.700 only
    • P633 version prior to P633.678.700
    • P438 version prior to P438.677.701
    • P632 version prior to P632.678.700
    • P634 version P634.680.700 only
    • P634 version prior to P634.678.700
    • P539 version prior to P539.678.700
    • P139 version prior to P139.678.700
    • C434 version prior to C434.679.700
    • P138 version prior to P138.677.700
    • P439 version prior to P439.678.700
    • P436 version prior to P436.677.701
    • P437 version prior to P437.678.700
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    • —
    Schneider ElectricEasergy MiCOM P40
    • Series model numbers with Protocol Option bit as G, H or L and all firmware versions
    • —
    Schneider ElectricEasyLogic T150 (formerly Saitel DR)
    • Version 11.06.30 and prior
    • —
    Schneider ElectricEcoStruxure™ Power Automation System Gateway (EPAS-GTW)
    • Version 6.4.616.200.100 and prior
    • —
    Schneider ElectricEcoStruxure™ Power Automation System User Interface (EPAS-UI)
    • Version 3.0.3 and prior
    • —
    Schneider ElectricEcoStruxure™ Power Operation
    • Version 2022 CU6 and prior
    • Version 2024 CU2 and prior
    • —
    • —
    Schneider ElectriciPMFLS
    • Version 64.2025.0.13 and prior
    • —
    Schneider ElectricPowerLogic™ P5 Protection Relay
    • V02.502.103 and prior
    • —
    Schneider ElectricPowerLogic™ P7 Protection and Control Platform
    • V02.002.002 and prior
    • —
    Schneider ElectricPowerLogic™ T300
    • Version 2.9.4 and prior
    • —
    Schneider ElectricPowerLogic™ T500
    • Version 11.08.02 and prior
    • —
    Schneider ElectricSaitel DP
    • Version 11.06.36 and prior
    • —
    Schneider ElectricEasergy MiCOM C434
    • C434.679.700
    • —
    Schneider ElectricEasergy MiCOM P138
    • P138.677.701
    • —
    Schneider ElectricEasergy MiCOM P139 version
    • P139.678.700
    • —
    Schneider ElectricEasergy MiCOM P439
    • P439.678.700
    • —
    Schneider ElectricEasergy MiCOM P539
    • P539.678.700
    • —
    Schneider ElectricEasergy MiCOM P632
    • P632.678.700
    • —
    Schneider ElectricEasergy MiCOM P633
    • P633.680.701
    • P633.678.700
    • P633.680.700
    • —
    • —
    • —
    Schneider ElectricEasergy MiCOM P634
    • P634.680.701
    • P634.680.700
    • —
    • —
    Schneider ElectricEcoStruxure Power Automation Automation System User Interface (EPAS-UI)
    • 3.0.4
    • —
    Schneider ElectricEcoStruxure Power Automation System Gateway (EPAS-GTW)
    • 6.4.610.500.101
    • —
    Schneider ElectricEcoStruxure Power Operation
    • 2022 CU7
    • —
    Schneider ElectricEcoStruxure Power Operation (EPO)
    • 2024 CU3
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-331Insufficient Entropy

      Base

      The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.

      Entry at MITRE CWE-331

    References & sources

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-4827
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-4827"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-4827.svg?lang=en" alt="CVE-2026-4827 – NEOSEC Intel" height="20"></a>