Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-pwhc-rpq9-4c8w

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

CVSS 7.3 HighEPSS 0.0017 · 6th percentile

Published by the GitHub Advisory Database at 6 Nov 2025, 15:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/containerd/containerdGo<1.7.291.7.29
github.com/containerd/containerd/v2Go<2.0.7 || >=2.1.0-beta.0, <2.1.5 || >=2.2.0-beta.0, <2.2.02.0.7, 2.1.5, 2.2.0
Identifiers
GHSA-pwhc-rpq9-4c8w · CVE-2024-25621 · GO-2025-4100
Weakness (CWE)
CWE-279
Tags
Published
6 Nov 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

containerd versions before 1.7.29 and 2.x versions before 2.0.7, 2.1.5 and 2.2.0 create some runtime and metadata directories with overly broad permissions. A local user on the host can access the metadata and content stores, and possibly the contents of Kubernetes local volumes, which could allow privilege escalation. Upgrade to 1.7.29, 2.0.7, 2.1.5 or 2.2.0, matching your release line; the update also corrects permissions on existing directories.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.3 High 3.1 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0017, the 6th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.