Incorrect Execution-Assigned Permissions Affecting k9s-fips package, versions <0.50.16-r3


Severity

Recommended
low

Based on default assessment until relevant scores are available.

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-CHAINGUARDLATEST-K9SFIPS-13860736
  • published8 Nov 2025
  • disclosed6 Nov 2025

Introduced: 6 Nov 2025

NewCVE-2024-25621  (opens in a new tab)
CWE-279  (opens in a new tab)

How to fix?

Upgrade Chainguard k9s-fips to version 0.50.16-r3 or higher.

NVD Description

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

containerd is an open-source container runtime. Versions 0.1.0 through 1.7.28, 2.0.0-beta.0 through 2.0.6, 2.1.0-beta.0 through 2.1.4 and 2.2.0-beta.0 through 2.2.0-rc.1 have an overly broad default permission vulnerability. Directory paths /var/lib/containerd, /run/containerd/io.containerd.grpc.v1.cri and /run/containerd/io.containerd.sandbox.controller.v1.shim were all created with incorrect permissions. This issue is fixed in versions 1.7.29, 2.0.7, 2.1.5 and 2.2.0. Workarounds include updating system administrator permissions so the host can manually chmod the directories to not have group or world accessible permissions, or to run containerd in rootless mode.