Improper Input Validation Affecting kubescape package, versions <4.0.9-r1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.48% (38th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-WOLFILATEST-KUBESCAPE-17393933
  • published22 Jun 2026
  • disclosed1 Jul 2026

Introduced: 22 Jun 2026

NewCVE-2026-53492  (opens in a new tab)
CWE-20  (opens in a new tab)
CWE-863  (opens in a new tab)

How to fix?

Upgrade Wolfi kubescape to version 4.0.9-r1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kubescape package and not the kubescape package as distributed by Wolfi. See How to fix? for Wolfi relevant fixed versions and status.

containerd is an open-source container runtime. In Versions prior to 2.3.2, 2.2.5 and 2.1.9, the CRI implementation improperly trusts Container Device Interface (CDI) annotations found within untrusted checkpoint image metadata during container restoration. When restoring a container from a checkpoint, containerd preserves CDI-related annotations from the checkpoint archive rather than relying solely on the pod's create-time specification. This allows a user with pod creation permissions to bypass standard Kubernetes resource allocation and device plugin enforcement, injecting arbitrary CDI edits (such as device nodes and host mounts) into the restored container. Successful exploitation requires that the node has CDI enabled and contains a matching host CDI specification for the requested device; environments where CDI is disabled or lacking sensitive device specifications are not affected. This issue has been fixed in versions 2.3.2, 2.2.5 and 2.1.9.