Deception Check

OT RESPONSE NOTES / EPICS BASE

The control network is trusted.
The software still needs a fix.

EPICS helps scientific facilities read instruments and control equipment. A flaw in how it handles network messages makes the next checks clear: who can connect, and is the fixed software running?

A device on an approved network can still send a message the software cannot safely handle.

EPICS is a toolkit for building scientific control systems, including those used at accelerators and light sources. An Input/Output Controller, or IOC, exposes readings and control functions to client software. The parser is the part of that software that reads incoming messages. A trusted network does not make every message safe.

7.0.10 and earlierAffected range listed by the CNA for EPICS Base. Check embedded and backported builds with their maintainer.
7.0.11The upstream release containing the fixes. Verify the process actually running after rollout.
9.8 / 9.3CVE-2026-114595 scores under CVSS v3.1 and v4.0 respectively.

The October 27 CISA advisory covers four flaws. For CVE-2026-114595, the CNA describes an integer overflow in a calculation used to reserve working memory. The result can wrap to an incorrect size, leaving too little space for the data processing that follows. The CNA lists memory corruption, service disruption, and potential code execution as consequences. It rates the network attack path as requiring no privileges or user interaction.

Three checks before you close the ticket

  1. Who can connect?Identify the IOC or protocol server, its owner, listeners, gateways, and source networks that can reach it. Include research workstations, remote access, and management paths.
  2. Which software is deployed?Record the EPICS Base build, Channel Access server, classic pvAccess components where present, and downstream fixes. A workstation package inventory alone can miss a custom IOC build.
  3. Which fixed version is running?Link the deployed binary and libraries to the running process after the approved restart or replacement. Retain the maintenance and functional-test receipts.

Use existing firewall rules, flow records, configuration, build manifests, and service-owner records first. Arrange any active reachability test through the facility's normal change process.

A permission check does not repair a message reader

EPICS supports IOC access-security rules; pvAccess also has authentication mechanisms. Cipher's research separates those controls from the vulnerable parsing paths: Channel Access write handling needs a TCP connection and a channel, while the pvAccess issue occurs during connection validation. The affected Channel Access write-notify path checks put permission before the unsafe sizing and conversion. Preserve those rules, check the configured channel permissions, and patch the vulnerable components.

ILLUSTRATIVE PATH / CVE-2026-114595 / CHANNEL ACCESS

  1. 01 / NETWORK PATHA client connects to the control service

    The write path needs a TCP connection and a channel. Configured access rules still apply.

  2. 02 / MESSAGE HANDLINGA message says how much data to process

    The software uses that count and the data type to reserve memory. The vulnerable calculation can reserve too little.

  3. 03 / MEMORY CORRUPTIONThe software writes beyond that space

    Cipher demonstrated memory corruption and a process crash in an instrumented test build. It did not demonstrate code execution.

  4. 04 / OPERATOR RESPONSELimit who can connect and install the fix

    Then verify the running build and test the clients the facility depends on.

Illustrative failure path based on the published research and upstream fix.

Match the fix to the component

Four CVEs, two protocol implementations. Scores are CVSS v3.1.
CVEComponentProblemScore
CVE-2026-114595Channel AccessInteger overflow in write-request sizing9.8
CVE-2026-114596Channel AccessExtended-message length overflow8.2
CVE-2026-114597Channel AccessElement count exceeds the received data7.5
CVE-2026-114598Classic pvAccess / pvDataCPPType confusion during deserialization7.5

The Channel Access fix in PR 934 strengthens validation between message size, data type, and element count. The pvDataCPP fix in PR 109 validates complex element types and bounds deserialization recursion. Ask downstream suppliers which changes their supported build includes.

Patch, then test the clients

Use EPICS Base 7.0.11 or a supported build containing the relevant backports. The EPICS release page warns that older Channel Access clients need interoperability testing, and that a successful compilation does not establish correct operation. Include the actual displays, scripts, gateways, archivers, and operational sequences the site relies on in the acceptance test.

When building from upstream source, use the project's complete release archive and verify its published signature. The maintainers explicitly warn that GitHub's automatically generated source archives omit the PVA submodules. Record the artifact and build recipe used, rather than only a download-page version.

If rollout must wait, narrow access to the hosts that need the service and assign an owner and date to the remaining exposure. An internal foothold can reach a poorly segmented controller even when the service is absent from the public internet.

What should a defender look for?

Unexpected connections

Compare traffic to the approved client and gateway inventory. Typical defaults are TCP 5064 for Channel Access and TCP 5075 for pvAccess; discovery commonly uses UDP 5064 and 5076. CA beacons/repeaters also use UDP 5065, and server TCP ports can be nondefault or dynamically selected. Confirm actual listeners and advertised paths before filtering.

A connection to one of these ports is a lead, not an exploit signature.

Unexpected process behavior

Review IOC or server crashes, restarts, core dumps, service-manager events, and parser errors. Correlate retained network records with the host, process, and time window.

A crash alone does not identify this CVE. An empty search is only useful when collection and retention are understood.

Preserve relevant logs off the affected host and coordinate containment with the operations owner. A lost IOC may interrupt monitoring or control functions; physical consequences depend on the facility's architecture and protection systems.

What the AI research adds

Causal Security says its Cipher system found and validated the four issues in 3 hours and 49 minutes. It describes one human instruction authorizing deeper sandbox testing. That is a useful example of AI-assisted security research; the task for operators is still a controlled, tested software change.

The public repository we inspected contains a version checker, not an overflow reproducer. CISA says no known public exploitation specifically targeting these flaws had been reported to the agency at advisory time.

RESPONSE WORKSHEET / TWO PAGES

Can you show who can connect and what is running?

Use the worksheet to capture the service, reachable networks, component build, patch receipt, legacy-client test, and next owner.

Download the response worksheet

Four-card response PDF ยท Read the card transcript

Our approach at Deception Check is to connect an unexpected interaction to the records and owner needed for a response. For an EPICS deployment, that starts with the facility's service and network evidence.

Sources and scope

This is Deception Check's response analysis of published research and maintainer guidance. We did not run an exploit, and no first-party EPICS attack captures are part of this report.