"The initial investigation required no human intervention, followed by one instruction authorizing deeper exploitability testing in a secure environment,"
said Shubham Raj, co‑founder of Causal Security, describing how an autonomous agent called Cipher discovered four previously unknown vulnerabilities in EPICS Base in three hours and 49 minutes. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) followed with a Tuesday advisory warning that successful exploitation could allow denial-of-service, memory corruption, disclosure of sensitive information, or potential remote code execution — and urging organizations to update to EPICS Base version 7.0.11, which includes the fixes.
Cipher’s autonomous discovery and prior work
Causal Security's Cipher independently investigated, tested and validated four security holes in the decades‑old, open source EPICS (Experimental Physics and Industrial Control System) toolkit. Raj described Cipher as “a fully autonomous super hacker that can reason across the technology stack.” According to Raj and reporting in The Register, Cipher required no human intervention for its initial investigation and then received a single instruction to carry out deeper exploitability testing in a secure environment.
This is not the first time Cipher's findings triggered government action: earlier this year, the agent identified multiple critical attack paths in power‑grid systems used across North America and Europe, prompting a CISA security advisory on October 8.
CVE-2026-114595: a critical, 9.8-rated integer overflow
The most severe of the newly disclosed flaws is CVE-2026-114595, rated 9.8 under CVSS v3.1. CISA and Causal Security describe it as an integer‑overflow vulnerability that permits attacker‑controlled network data to cause an out‑of‑bounds heap write. That condition can lead to memory corruption and — in the worst case — remote code execution.
Raj emphasized the operational impact: “EPICS controllers sit between operators and physical equipment, handling measurements, commands, and control functions. Operationally: Imagine a particle accelerator in the middle of an expensive experiment. An attacker could potentially crash a controller, interrupt critical measurements or control functions, and force operators to halt the experiment. That could mean lost experimental work, significant downtime, and expensive recovery.”

Audit-ready is a season. It shouldn't be.
Evidence in spreadsheets, controls drifting between audits, frameworks multiplying on flat headcount. Nubivance runs continuous compliance on Rapid7 Cyber GRC - SOC 2, HIPAA, ISO 27001, PCI, CMMC.
End the scrambleThe three other high‑severity EPICS Base bugs
- CVE-2026-114596 — CVSS 8.2. An improper message‑length validation flaw that can cause an out‑of‑bounds memory write and crash controller processes.
- CVE-2026-114597 — CVSS 7.5. An insufficient bounds‑checking bug that permits out‑of‑bounds memory reads and process crashes.
- CVE-2026-114598 — CVSS 7.5. A type‑confusion flaw that can lead to denial of service and the exposure of adjacent memory contents.
All four vulnerabilities affect EPICS Base and were disclosed with fixes in EPICS Base 7.0.11. CISA's advisory lists the potential impacts — denial of service, memory corruption, disclosure, and possible code execution — and directs organizations to apply the update.
EPICS Base: where it runs and how that shapes risk
EPICS was originally developed by Los Alamos National Laboratory and Argonne National Laboratory and is used to build and remotely control distributed SCADA systems that connect operators to physical devices. Causal Security and CISA note that EPICS is used in roughly 90 major scientific, university and industrial projects and facilities worldwide, including Argonne National Laboratory's Advanced Photon Source and the ITER fusion reactor control system.
Exploitation in real facilities requires the attacker to reach vulnerable EPICS services on a facility's control network. Causal Security warned that this can happen if networks are not sufficiently segmented or if another system has access to the EPICS network.
What this means for technologists, facility operators, and adversaries
- Technologists and security teams: CISA's advisory explicitly recommends updating to EPICS Base 7.0.11; teams will also need to verify network segmentation and access controls for EPICS services to reduce the chance that an attacker can reach vulnerable controllers.
- Facility operators and researchers: Because EPICS controllers mediate commands and measurements, operators face the risk of interrupted experiments, crashed controller processes, and lost operational data even if an attacker does not achieve remote code execution.
- Adversaries and exploit developers: Causal Security warns that exploiting these vulnerabilities does not demand deep operational‑technology expertise; conventional exploitation skills combined with increasingly capable AI systems could reveal and weaponize weaknesses without specialized knowledge of the physical processes controlled by EPICS.
The record in this case is clear: an autonomous agent found multiple high‑impact flaws in a toolkit that underpins dozens of major scientific and industrial projects, and CISA has issued an advisory that includes an explicit mitigation — upgrade to EPICS Base 7.0.11. For defenders, the immediate steps are concrete; for the broader security community, the episode underscores a broader concern voiced by Causal Security and CISA alike: as AI agents grow more capable, the timeframe from discovery to weaponization of operational‑technology vulnerabilities is shrinking. Organizations that run EPICS must now decide how quickly to apply the patch and whether their network architectures are sufficiently robust to keep exposed controllers out of reach.




