CODESYS SBOM: recording runtime, add-ons and libraries per controller
In brief · As of November 2026
Besides the device manufacturer's firmware, a CODESYS controller has three version layers of its own: the runtime (CODESYS Control), the add-ons in the device tree such as PROFINET, EtherNet/IP, Modbus and visualization, and the libraries in the library manager. CODESYS publishes advisories for all three as CSAF via CERT@VDE: 36 documents since 2023, 12 of them in 2026. For four of the twelve from 2026 and for the advisory on the OSCAT library, a firmware update does not help. The fix requires raising the component version in the project and downloading the application to the controller again; only whoever holds the PLC project can do that, usually the plant builder. If the runtime is part of the device firmware, the device manufacturer's advisory comes late: at WAGO a median of 238 days after CODESYS. The device list therefore has to carry runtime, add-ons and libraries with version for every CODESYS controller, taken from the project, because no network scan sees add-ons and libraries.
Besides the firmware, a CODESYS controller has three version layers of its own
CODESYS is not a device but software built into controllers from many manufacturers. A WAGO PFC200, a controller from ifm or an industrial PC with CODESYS Control Win therefore carry several versions that age independently of each other:
- Device manufacturer's firmware: operating system, drivers and usually a built-in CODESYS runtime. At WAGO, the runtime is part of the controller firmware; a runtime fix arrives there with a new firmware release.
- Runtime as a product of its own: CODESYS also sells the runtime directly, for example as CODESYS Control Win for Windows PCs, Control RTE, Control for Linux SL or Control for PFC200 SL for WAGO hardware. It then has a version number of its own, independent of the device firmware.
- Add-ons in the device tree: fieldbus and communication stacks (PROFINET, EtherNet/IP, Modbus, OPC UA) and the visualization. They travel with the application to the controller and have versions of their own, such as CODESYS PROFINET 4.8.0.0.
- Libraries: standard libraries from CODESYS, libraries from device and drive manufacturers, open source libraries such as OSCAT, and in-house ones. They, too, travel with the application to the controller.
An advisory can hit any of these layers. Which one is stated in the product tree: “CODESYS Control Win (SL)”, “CODESYS PROFINET” or “OSCAT Basic Library”. A device list that carries only order number and firmware per controller cannot match any of them.
CODESYS publishes CSAF via CERT@VDE, a third of the 2026 advisories concern add-ons
CODESYS publishes as a trusted provider at CERT@VDE: provider-metadata.json with ROLIE feed and index.txt, released for mirroring on aggregators. On 3 Nov 2026 we downloaded the complete feed and counted the documents by affected product.
| Measurement (3 Nov 2026) | Result |
|---|---|
| CSAF advisories total | 36; the feed starts in 2023 |
| Initial releases 2023 / 2024 / 2025 / 2026 | 8 / 5 / 11 / 12 |
| 2026: runtime (CODESYS Control) | 5 |
| 2026: add-ons (EtherNet/IP, Modbus, PROFINET, visualization) | 4 |
| 2026: development system, installer, gateway | 3 |
| Documents naming CODESYS Control Win | 17 of 36 |
| Advisories on libraries | 1 (VDE-2024-046, OSCAT Basic) |
| Documents with CPE / PURL / order numbers | 2 / 0 / 0 |
In the feed, products carry the names under which CODESYS sells them, with a version range: CODESYS PROFINET >=4.4.0.0|<4.8.0.0, CODESYS Modbus <4.6.0.0. Device manufacturers and their order numbers do not appear in the CODESYS advisories. Which controller has an affected runtime built in is only stated in the device manufacturer's advisory, if there is one.
For add-ons and libraries, the plant builder deploys the fix, not the device manufacturer
For the four add-on advisories from 2026, CODESYS gives the same remedy: update the add-on, raise the component in the project's device tree to the new version and download the application to the controller again. For the visualization, the fix takes effect only after recompiling and downloading. For the advisory on the OSCAT Basic library (CVE-2024-6876) it is the library manager: enter version 3.3.5.0, download the application again.
A firmware update from the device manufacturer changes nothing here. The vulnerable version sits in the application, and the application belongs to the plant builder's project. Anyone who does not know the project versions of their delivered plants does not know which controller has an affected PROFINET or OSCAT version loaded, and can neither assess nor deliver a fix.
Advisories on PLC libraries are rare: in the CODESYS feed, one of 36 concerns a library. OSCAT is an open source project; CODESYS reported it via CERT@VDE. The version list per controller is still needed, because when such an advisory arrives it is the only way to find the affected plants. For in-house libraries the same applies with reversed roles: here the plant builder is the manufacturer who assesses and reports a vulnerability.
At WAGO, the advisory for the built-in runtime follows a median of 238 days after CODESYS
If the runtime is part of the device firmware, an advisory from the device manufacturer is needed that names its own order numbers and the firmware release with the fix. The WAGO feed shows how long that takes: 20 of the 83 WAGO advisories mention CODESYS (as of 3 Nov 2026). For the six most recent cases we counted the gap to the CODESYS advisory for the same CVE.
| CODESYS advisory | date | WAGO advisory | date | days |
|---|---|---|---|---|
| VDE-2023-066 (command injection) | 5 Dec 2023 | VDE-2025-008 | 4 Feb 2025 | 427 |
| VDE-2024-026 (OPC UA) | 4 Jun 2024 | VDE-2025-009 | 4 Feb 2025 | 245 |
| VDE-2024-057 (web server) | 25 Sep 2024 | VDE-2024-072 | 3 Dec 2024 | 69 |
| VDE-2025-015, -022 (path, OPC UA) | 18 Mar 2025 | VDE-2025-062 | 3 Nov 2025 | 230 |
| VDE-2025-027 (WebVisu) | 23 Apr 2025 | VDE-2025-062 | 3 Nov 2025 | 194 |
| VDE-2025-099, -100, -101 | 1 Dec 2025 | VDE-2025-081 | 1 Oct 2026 | 304 |
The median is 238 days. During that time no WAGO document names the affected controllers. Anyone who keeps the built-in runtime version in the device list alongside order number and firmware release can match the CODESYS advisory on the day it is published. How other device manufacturers behave is shown in the manufacturer comparison.
Runtime, add-ons and libraries are recorded in the project, not on the network
A network scan sees at best device and firmware of a CODESYS controller. Add-ons and libraries are known only to the project and the loaded application:
- PLCopenXML export of the project: it contains the library references with name, vendor and version and the device tree. This is the simplest machine-readable route to the library list.
- Placeholders with an asterisk: if “*” is entered instead of a version, CODESYS uses the newest version installed on the engineering PC at compile time. Which one that was is then known only to the computer the project was compiled on. Delivered plants need fixed versions in the project.
- Device tree: add-ons such as the PROFINET controller, EtherNet/IP adapter or Modbus server are listed there with their version; the runtime version of the target follows from the device description.
- Windows inventory for CODESYS Control Win and Control RTE on industrial PCs: the runtime appears among the installed programs with its version. More on this in the article on Windows on the industrial PC.
In the plant SBOM this becomes a subtree: the device with order number and firmware, below it the runtime, below that add-ons and libraries with name, vendor and version. CPE and PURL practically do not exist for these components; the CODESYS advisories identify by product name and version range, and that is exactly how the list has to carry the components.
For the plant, four versions per CODESYS controller count
- Device with order number and firmware release, as for any other device.
- Runtime: built in, with the version the device manufacturer ships, or as a product of its own with its own version.
- Add-ons from the device tree with their version.
- Libraries from the library manager with a fixed version, including third-party and in-house libraries.
This includes following both sources: CODESYS for runtime and add-ons, the device manufacturer for the firmware. Anyone who waits only for the device manufacturer loses a median of eight months in the WAGO example.
Werkspilot reads the PLCopenXML export of a CODESYS project and carries runtime, add-ons and libraries as components of the controller, separate from device and firmware.
All 13 manufacturers compared: SBOM by manufacturer →
Guide: the plant SBOM in five steps.
Which sources feed the device list, which version layers count per device and how matching against manufacturer advisories works without CPE, compact as a PDF with a checklist per step.
Werkspilot keeps the devices of delivered plants and reports when a manufacturer advisory hits one of them by order number and firmware. It reads runtime, libraries and Windows versions and carries them per device. The figures in this article are our own measurements from 3 Nov 2026; manufacturers change feeds and documents without notice.
