CVE-2026-24260: NVIDIA Container Toolkit for Linux contains a vulnerability where an attacker could cause a time-of-check time-of-use race condition. (3rd July 2026)

Preface: The core difference between the NVIDIA Container Toolkit and the NVIDIA GPU Operator is their scope of management: the NVIDIA Container Toolkit is a low-level component that enables individual container runtimes (like Docker or containerd) to talk to a local GPU, while the NVIDIA GPU Operator is a high-level orchestration system that automatically deploys and manages that toolkit—along with drivers and monitoring software—across an entire Kubernetes cluster.

Background: The NVIDIA Container Toolkit is a collection of libraries and utilities that allows containers (like Docker, Podman, and Kubernetes) to automatically detect and leverage NVIDIA GPUs. It handles the heavy lifting of mapping GPU devices and mounting necessary driver libraries directly into the container.

The toolkit is made up of a few core components that work together behind the scenes:

•NVIDIA Container Toolkit CLI (nvidia-ctk): The main command-line tool used to configure container runtimes to use NVIDIA GPUs. It sets up the backend configurations for tools like Docker, containerd, and CRI-O.

•NVIDIA Container Runtime (nvidia-container-runtime): A wrapper around standard low-level container runtimes (like runC) that injects the required GPU devices and drivers when a container starts.

•NVIDIA Container CLI (nvidia-container-cli): The low-level utility that inspects the host environment, enumerates GPUs, and configures the container execution environment.

•NVIDIA Container Library (libnvidia-container): The underlying programming library that provides the API to construct and manage the GPU-accelerated containers.

•NVIDIA CDI Hooks (nvidia-cdi-hook): Uses the open standard Container Device Interface (CDI) to seamlessly specify and allocate GPU devices to containers.

Vulnerability details: CVE-2026-24260 NVIDIA Container Toolkit for Linux contains a vulnerability where an attacker could cause a time-of-check time-of-use race condition. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, and data tampering.

Official announcement: Please refer to the link for details – https://nvidia.custhelp.com/app/answers/detail/a_id/5850

CVE-2026-13592: Vulnerability was detected in liftoff-sr CIPster, Rockwell/Allen Bradley PLCs), you must be vigilant! (30-6-2026)

Preface: CIPster is an EtherNet/IP™ stack because it provides the software architecture required to implement the Common Industrial Protocol (CIP) over standard Ethernet, TCP, and UDP networks.

Background: CIPster is an open-source, EtherNet/IP™ stack written in C++.

  • Its Role: It is maintained under the GitHub organization liftoff-sr. It allows a Linux-based device to emulate an industrial “slave/adapter” device.
  • Its Scope: It only handles communication over EtherNet/IP (the Common Industrial Protocol or CIP, commonly used by Rockwell/Allen-Bradley PLCs). It does not natively handle cloud ingestion, database logging, or security protocols required for cloud routing.

To handle communication over EtherNet/IP, liftoff-sr/CIPster exposes an initialization and execution loop API. Because CIPster is a C++ port of the C-based OpENer stack, its implementation follows a structured lifecycle: initializing the adapter, registering assembly objects (I/O tags), and feeding data into a network socket service loop.

Vulnerability details: A vulnerability was detected in liftoff-sr CIPster up to e8e9dba09bf56962807d3504b783ccdb6287f3e4. Affected by this issue is the function BufWriter::append of the component EtherNet IP Message Handler. Performing a manipulation results in out-of-bounds write.

Impact: Remote exploitation of the attack is possible. The exploit is now public and may be used.

Recommendation: This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided.

The patch is named 3a0159ed43125dcd024a1965f0289cb186bae9ff. To fix this issue, it is recommended to deploy a patch.

Official announcement: Please refer to the link for details – https://www.tenable.com/cve/CVE-2026-13592

https://github.com/liftoff-sr/CIPster/issues/48