Integer Overflow and Out-of-Bounds Write in EPICS Base Protocol Parsing
CVE-2026-114596 affects EPICS Base 7.0.10 and earlier. Improper validation of message-length values during network protocol parsing can trigger an integer overflow, resulting in an out-of-bounds memory write. An unauthenticated attacker with network access to a vulnerable service can exploit the flaw without user interaction, causing process instability or denial of service.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Exploitation can corrupt process memory, destabilize an EPICS process, or crash it, resulting in denial of service. In control-system deployments, an affected controller-process crash could interrupt measurements, monitoring, or control functions and halt experiments. The vulnerability is assessed as having high availability impact, low integrity impact, and no confidentiality impact. Remote code execution is not established for this CVE.
If you can’t patch tonight, do this now.
Minimize network exposure of EPICS services and prevent direct internet access. Place control-system networks and remote devices behind firewalls, isolate them from business networks, and restrict access to authorized systems. Where remote access is necessary, use secure, updated VPN infrastructure. Perform operational impact analysis and risk assessment before deploying defensive changes.
Patch, then assume compromise.
Upgrade affected installations from EPICS Base 7.0.10 or earlier to EPICS Base 7.0.11, which includes the fix.
No public exploits tracked yet. Mallory keeps watching.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.