dbcve.org
ContainerdApplication · Linuxfoundation

CVE-2024-25621

HIGH · 7.8 CVSS v3.1 Published 2025-11-06
Fix available
A fix is available. Upgrade to 1.7.29 / 2.0.7 or later.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ContainerdApplication
Affected:< 1.7.29>= 2.0.0, < 2.0.7>= 2.1.0, < 2.1.5= 2.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.7.29 / 2.0.7 / 2.1.5 or later
Fixed in 1.7.292.0.72.1.5
Vendor patch github.com →
Recommended fix High confidence

Upgrade to containerd 1.7.29 (for 1.x), 2.0.7 (for 2.0.x), 2.1.5 (for 2.1.x), or 2.2.0 (for 2.2.x) - choose the version that corresponds to your current major.minor branch

  1. 1. Identify your current containerd version by running: ctr version or containerd --version
  2. 2. Stop the containerd service: systemctl stop containerd (or the equivalent for your init system)
  3. 3. Upgrade containerd to the fixed version that matches your major release branch: For 1.x users, upgrade to 1.7.29 or later; For 2.0.x users, upgrade to 2.0.7 or later; For 2.1.x users, upgrade to 2.1.5 or later; For 2.2.x users, upgrade to 2.2.0 or later
  4. 4. If upgrading via package manager (apt, yum, dnf), run: apt-get update && apt-get install containerd (or corresponding package manager command)
  5. 5. Start the containerd service: systemctl start containerd
  6. 6. Verify the fix by checking permissions on the affected directories: ls -la /var/lib/containerd, ls -la /run/containerd/io.containerd.grpc.v1.cri, ls -la /run/containerd/io.containerd.sandbox.controller.v1.shim - directories should NOT have group (g) or world (o) read/write/execute permissions (should be 700 or similar restrictive permissions)
Caveat Upgrading containerd within the same major.minor series typically has minimal breaking changes; however, always review release notes for any configuration or runtime behavior changes before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25621 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25621 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data