CVE-2024-25621CWE-279

containerd affected by a local privilege escalation via wide permissions on CRI directory

High · published November 6, 2025

CVSS v3.1
7.3
EPSS
0%
Percentile
5.8
In the wild
Unconfirmed
What it is

⚡ A misconfigured container runtime could let unauthorized users run amok! This overly broad permission vulnerability in containerd affects a range of recent versions, putting the security of your containers in jeopardy! 🔥 Think of it like a storage facility where the doors to all the units are left unlocked. Anyone can waltz in and grab whatever they want, which is exactly the risk when essential directories such as `/var/lib/containerd` have incorrect permissions in containerd. An attacker could exploit this vulnerability to access sensitive data and potentially alter container configurations, leading to compromised applications and security breaches. With unauthorized access, the effects could cascade through your infrastructure, resulting in a security nightmare that could have been avoided!

Put simply

Think of it like a storage facility where the doors to all the units are left unlocked. Anyone can waltz in and grab whatever they want, which is exactly the risk when essential directories such as `/var/lib/containerd` have incorrect permissions in containerd. This vulnerability arises from overly permissive default settings in containerd's directory paths, allowing users and groups without proper authorization to gain access to critical system directories. This opens the door for security risks, as those directories can contain sensitive data or configurations.

What to do

An attacker could exploit this vulnerability to access sensitive data and potentially alter container configurations, leading to compromised applications and security breaches. With unauthorized access, the effects could cascade through your infrastructure, resulting in a security nightmare that could have been avoided! Update containerd to versions 1.7.29, 2.0.7, 2.1.5, or 2.2.0 to secure your environment. Alternatively, system administrators can manually adjust permissions on the affected directories to restrict access or consider running containerd in rootless mode to enhance security. You're on the right track! Follow these steps and you'll have your container environment fortified in no time. 🛡️

The record
Technical detail
CVSS v3.1
7.3 · HIGH
Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
CVSS v4.0
Not supplied
EPSS
0.00168 · 5.8th percentile
Weakness
CWE-279 · Incorrect Execution-Assigned Permissions
Published
2025-11-06T18:36Z
EPSS history
Timeline
  • 06 NOV 18:36Z
    containerd affected by a local privilege escalation via wide permissions on CRI directory
    cvelistv5