Skip to content
audiotale.net
Sign in
NewsNews

CVE-2026-114595: EPICS Base flaws, found by an AI agent in under 4 hours, hit lab control systems

CISA advisory ICSA-26-300-01 lists four flaws in EPICS Base 7.0.10 and earlier, one rated CVSS 9.8; the fix is 7.0.11.

audiotale.net team

· 7 min read

Written by AI from the sources linked below. How we use AI

On this page
  1. Key points
  2. What to do
  3. What happened
  4. Background
  5. The numbers
  6. What it means
  7. What we don't know yet
  8. What to watch next
  9. Sources

CISA published advisory ICSA-26-300-01 on 27 October 2026 covering four flaws in EPICS Base, the open source toolkit behind the control systems of many particle accelerators, telescopes and fusion experiments. The worst, CVE-2026-114595, scores 9.8 out of 10 and could let a remote attacker run code on a controller. All four affect EPICS Base 7.0.10 and earlier, and the advisory tells users to move to 7.0.11. The bugs were found by an autonomous AI agent, which makes this as much a story about how fast machines now find flaws in obscure industrial software as about the flaws themselves.

Key points

  • CISA advisory ICSA-26-300-01 (27 October 2026) lists CVE-2026-114595, CVE-2026-114596, CVE-2026-114597 and CVE-2026-114598 in EPICS Base 7.0.10 and earlier.
  • CVE-2026-114595, an integer overflow in network request processing, is rated CVSS 3.1 9.8 (Critical) and CVSS 4.0 9.3; the other three are rated 8.2, 7.5 and 7.5 on CVSS 3.1.
  • CISA says affected users should update to EPICS Base 7.0.11 and that it knows of no public exploitation of these flaws.
  • CISA credits Shubham Raj of Cipher / Causal Security; The Register reports that the Cipher AI agent found all four in 3 hours 49 minutes.
  • Exploitation needs network access to the vulnerable EPICS services, so segmentation of control networks is the main defence until patches are applied.

What to do

Who is affected: anyone running EPICS Base 7.0.10 or earlier, which the advisory lists as the affected range. CISA files the product under the Critical Manufacturing sector, but EPICS is used mostly in research facilities, universities and industrial projects.

Fix: update to EPICS Base 7.0.11, as the EPICS Community told CISA. The advisory links patches in the epics-base repository (pull requests 934 and 937) and in pvDataCPP (pull request 109). When we checked the EPICS Controls news page on 28 October, it still listed 7.0.10 (11 February 2026) as the latest Base release and had no announcement for 7.0.11, so take the release from the project's download page or its repository and check the version yourself.

If you cannot patch yet: follow CISA's general guidance. Keep control system networks off the internet, put them behind firewalls and separate them from business networks, and use an updated VPN for any remote access. The Register's reporting makes clear that the prerequisite for an attack is reaching the vulnerable EPICS services on the control network, so a flat or misconfigured network is the real risk.

How to check: run the version query for your IOCs and gateways and compare against 7.0.10. If any host that speaks the EPICS network protocols is reachable from a network segment you do not fully trust, treat it as exposed until it is updated.

What happened

CISA's advisory, published on 27 October 2026 as revision 1, lists four vulnerabilities in EPICS Base:

  • CVE-2026-114595 (CWE-190, integer overflow): an integer overflow in network request processing causes memory to be allocated with an incorrect size. CVSS 3.1 9.8 Critical, vector AV:N/AC:L/PR:N/UI:N, with high impact on confidentiality, integrity and availability. CVSS 4.0 gives it 9.3.
  • CVE-2026-114596 (CWE-190): improper message length validation during protocol parsing causes an integer overflow and an out-of-bounds write. CVSS 3.1 8.2 High; CVSS 4.0 8.8.
  • CVE-2026-114597 (CWE-130): insufficient validation of element or length values lets code read beyond an allocated buffer. CVSS 3.1 7.5 High; CVSS 4.0 8.7.
  • CVE-2026-114598 (CWE-843, type confusion): the same family of over-read behaviour, rated 7.5 on CVSS 3.1 and 8.7 on CVSS 4.0.

All four are reachable over the network with low complexity, no privileges and no user interaction, according to the CVSS 3.1 vectors CISA publishes. The advisory says successful exploitation could cause denial of service, memory corruption, disclosure of sensitive information or, potentially, arbitrary code execution. CISA's page header says "3 Vulnerabilities" while listing four, an inconsistency in the advisory, not in the CVE list.

The Register, which spoke to the researcher, reports that an AI agent called Cipher, built by Causal Security, found all four previously unknown flaws, investigating the unfamiliar EPICS code base and validating the exploits in three hours and 49 minutes. Co-founder Shubham Raj told the outlet that the initial investigation needed no human intervention, followed by one instruction authorising deeper exploitability testing in a secure environment. Those timings and the description of the process are the company's account; CISA's advisory credits Raj with reporting the flaws but does not describe how they were found.

Background

EPICS, the Experimental Physics and Industrial Control System, was originally developed at Los Alamos National Laboratory and Argonne National Laboratory. It is a software toolkit for building distributed SCADA-style systems: input/output controllers read sensors and drive devices, and operator stations talk to them over the network. The Register says it is used in around 90 major scientific, university and industrial projects, including Argonne's Advanced Photon Source and the control system of the ITER fusion project. We have not independently verified that count.

The project's own release history shows a steady cadence of 7.0.x releases: 7.0.9 in February 2025 and 7.0.10 on 11 February 2026, according to the EPICS Controls news archive. The patches CISA references predate the advisory by months. Pull request 934 in epics-base, titled "RSRV message validation" and authored by maintainer Michael Davidsaver, was merged into the 7.0 branch on 23 July 2026. RSRV is the Channel Access server in EPICS Base, and the pull request describes extending validation of messages to reduce the risk of malicious input, with the goal of preventing integer overflows and cross-checking the message size, data type and count fields. Pull request 937, merged on 22 July 2026, only adds a SECURITY.md file describing how to report problems. CISA lists both as patch references but does not say which CVE each addresses, so we cannot map individual bugs to individual commits.

Causal Security's agent has been in this territory before. The Register says it earlier this year found attack paths in power-grid systems in North America and Europe, which led to a CISA advisory on 8 October. That fits a broader pattern of defenders warning that systems which once relied on obscurity are now being probed by automated tools.

The numbers

The four scores below are the CVSS 3.1 base scores from CISA's advisory. Scores on the newer CVSS 4.0 scale are higher for the three lower-ranked flaws (8.8, 8.7 and 8.7) and lower for the top one (9.3).

EPICS Base flaws by CVSS 3.1 base scoreCVSS 3.1 score
EPICS Base flaws by CVSS 3.1 base score (CVSS 3.1 score)
CVSS 3.1 score
CVE-2026-1145959.8
CVE-2026-1145968.2
CVE-2026-1145977.5
CVE-2026-1145987.5

Source: CISA advisory ICSA-26-300-01

The scores rank flaws by technical severity, not by risk to a given site. Because EPICS control networks are normally isolated, the practical risk depends on whether an attacker can reach the vulnerable services at all. The CVSS vectors assume a network attacker; they say nothing about whether your network lets one in.

What it means

For facility operators. The patch is a drop-in version bump in principle, but control systems are rarely patched casually: a running accelerator or beamline is not restarted for an advisory. Plan the update for the next maintenance window, and in the meantime verify segmentation. If an EPICS gateway bridges a lab network to a wider campus network, that bridge is the first place to look.

For software maintainers. The fixes were merged into the public 7.0 branch in July, three months before the advisory. Anyone watching the repository could have seen validation changes for message fields; a patch published before an advisory is a hint for attackers as well as defenders. That is the usual argument for coordinating releases and advisories closely, and it applies to open source control software as much as to anything else.

For security teams. Raj's account, that an agent can go from an unfamiliar code base to validated exploits in under four hours, is the claim to take seriously, with the caveat that it comes from the vendor selling the agent. The advisory says nothing about the method. If it holds up, the cost of auditing niche industrial and scientific software has dropped, and the long tail of little-reviewed OT code is where that matters most. Raj also said exploiting these bugs would not need deep OT knowledge: conventional exploitation skills would do for crashing or disrupting a controller, while manipulating a specific physical process needs more domain knowledge.

What we don't know yet

  • The exact release date of 7.0.11. CISA names the version; the EPICS news page we checked did not list it. One secondary report says it came out the same day as the advisory, but we could not confirm that against the project.
  • Which protocol each CVE sits in. CISA does not say whether the flaws are in Channel Access, pvAccess or shared libraries. The pvDataCPP patch reference suggests the pvAccess side is involved as well, but that is our inference.
  • Whether the bugs are being exploited. CISA reports no known public exploitation at the time of publication. That can change quickly once patches are public.
  • How many exposed instances exist. The Register quotes roughly 90 major projects; no source we found counts EPICS services reachable from the internet.
  • Independent verification of the AI agent's timeline. The three hours and 49 minutes figure is Causal Security's.

What to watch next

Watch for the EPICS 7.0.11 release notes and any backports to the 3.15 series, for updates to CISA's advisory (new revisions often add exploitation status), and for exploit write-ups from Causal Security or others. Also watch whether more of these AI-found advisories land on other scientific and industrial toolkits in the coming weeks.

Sources

SaveStart the discussion

Written by

audiotale.net team

The official account of the people who run audiotale.net: announcements, conversation starters and the newsroom's drafts. Posts written with AI say so. Every other account here is a real person.

Read next