Skip to content

Release notes

This page contains a list of features, changes, known issues and known limitations of the Nerve releases.

Version 2.6.1

This version was released on May 5, 2023. It provides security relevant updates. Unless otherwise stated, all known issues and limitations of the previous version are still valid.

Security patch details

Short description Log system accessible without authentication.
CVSS score CVSS Score: 9.4
Version All Management Systems lower than 2.6.1.
Description The /filebeat_app/ route on any Nerve Management System is unprotected and open to the public. This open route can be used to create OpenSearch indices, which can be used for denial of service attacks.
Actions to be taken Note that nodes with versions lower than 2.6.1 are not able to transmit logs to Management Systems with versions 2.6.1 and higher anymore.
Risks if the patch is not applied The vulnerability may be exploited to render the system unavailable or leak and manipulate logs and metrics from the node. In case of further questions or need of assistance in applying the patch, contact TTTech Industrial customer support.


  • Improved the system's behavior in high load situations.
  • Improved the system's behavior when a DNA configuration is in progress.
  • Time zone formats have been cleaned up to ease time zone configuration of nodes.
  • Improved the robustness of the CODESYS runtime.
  • Improved the robustness of the license activation components.
  • Added new functions and calls to the Management System API.

Bug fixes

  • Fixed an issue where PCIe devices were not propagated into the RTVM.
  • Fixed an issue where a high load on Docker workloads would cause the CODESYS runtime to crash.
  • Fixed an issue where copying workload details containing a number in name or version, e.g. version: 1, into a DNA configuration file would produce an invalid file.
  • Fixed an issue where nodes would crash if a workload was deployed from the Management System UI while Nerve DNA reconfiguration was in progress.
  • Fixed an issue where removing workloads that were successfully deployed to a node through Nerve DNA while reconfiguration is in progress would result in the node wrongly entering the Applied state instead of the Modified state.
  • Fixed an issue where the Local UI component would be stuck in a reset loop after a reboot.
  • Fixed an issue where Nerve networks could not be used with Docker Compose workloads.

Known issues and limitations

  • Marking a workload as released changes the hash of the workload.
  • A workload with the same name as an already existing workload can be created through the Management System API.
  • Icons in Action columns appear smaller than intended in some tables.
  • docker-compose cannot be used as a workload type for the endpoint PATCH /nerve/v2/workloads/{workloadId}, even though it is present among the possible values. The V3 endpoint must be used for Docker Compose workloads.
  • The Nerve Connection Manager fails on Linux with Management Systems using self-signed certificates.
  • The creation of VM workload versions through the use of API might lead to the creation of unusable workloads.
  • Remote connections are wrongly shown as active in the Nerve Connection Manager when they are disconnected due to bad network quality.
  • The Nerve Data Services Gateway does not transmit values correctly if it receives data in nested structures using the default OPC UA structure type. Substructures need to be of the custom structure data type.
  • Nodes sometimes still appear in the node tree even though they have been removed from the Management System. This can occur due to changes in different sessions in the same Management System.
  • The workload creation or update using the v2 route in the API does not work with Swagger. This is particularly problematic with VM workloads, as Swagger only has one field for required files, while VM workloads demand an XML and an image file.
  • Nodes with versions lower than 2.6.1 are not able to transmit logs to Management Systems with versions 2.6.1 and higher anymore.
  • Deployment of workloads and fetching workload lists behaves erroneously in air-gapped Management Systems when the versions between the Management System and the node do not match.
  • Resource indicators for Docker Compose workloads do not work in the Local UI. RAM and CPU values always show 0%.

Scaling and performance limitations

This release has been tested to perform within the following scaling boundaries:

Maximum number of concurrent devices 200 
Maximum number of concurrently logged in users
Maximum workload size 50 GB 
Maximum number of concurrent remote access sessions
Maximum number of workloads in workload repository 200
Maximum data upload per node 5 datagrams per second with at least 10 sensor values for 200 nodes in parallel.