CVSS 3.1
7.8 highCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HHigh (7.8) in containerd containerd. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/containerd/containerd/v2 2.2.7, 2.3.4.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hgithub.com/containerd/containerd/v2 (Go): fixed in 2.2.7, 2.3.4Explain CVE-2026-95837 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-95837?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-95837?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-95837 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| containerd | >= 2.1.0, < 2.2.7 |
| containerd | >= 2.3.0, < 2.3.4 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-p7v4-vr35-mj6f | Go | github.com/containerd/containerd/v2 | >=2.1.0 <2.2.7 | 2.2.7 |
| GHSA-p7v4-vr35-mj6f | Go | github.com/containerd/containerd/v2 | >=2.3.0 <2.3.4 | 2.3.4 |
| GO-2026-6791 | Go | github.com/containerd/containerd | all versions | no fix published |
| GO-2026-6791 | Go | github.com/containerd/containerd/v2 | >=2.1.0 <2.2.7 >=2.3.0 <2.3.4 | 2.2.7, 2.3.4 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | containerd | no fix listed | DEBIAN-CVE-2026-95837 |
| Ubuntu | 22.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS and 2 more | containerd | no fix listed | UBUNTU-CVE-2026-95837 |
| Ubuntu | 24.04:LTS, Pro:22.04:LTS | containerd-app | no fix listed | UBUNTU-CVE-2026-95837 |
| Ubuntu | 26.04:LTS | containerd-app, containerd-stable | no fix listed | UBUNTU-CVE-2026-95837 |
| Ubuntu | 26.10 | containerd, containerd-app, containerd-stable | no fix listed | UBUNTU-CVE-2026-95837 |
| Ubuntu | Pro:20.04:LTS | containerd, containerd-app | no fix listed | UBUNTU-CVE-2026-95837 |
| SUSE | Linux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0 | govulncheck-vulndb | 0.0.20261105T234957-160000.1.1 | SUSE-SU-2026:24730-1 |
| Alpaquita | 25 | containerd | 2.2.8-r0 | BELL-CVE-2026-95837 |
| Alpaquita | stream | containerd | 2.3.5-r0 | BELL-CVE-2026-95837 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · Alpaquita.
Red Hat rates this Important.
This vulnerability is rated Important rather than Moderate because an authenticated user with container creation privileges can achieve unconfined root privileges and disable seccomp protections while orchestrator auditing continues to report the restricted profile. In typical Red Hat environments, core container management platforms rely on CRI-O rather than containerd, significantly restricting the scope of affected deployments. Furthermore, exploitation is strictly contingent on leveraging CRI checkpoint restoration workflows, meaning environments that do not utilize container checkpointing are not exposed to this risk.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | git-sync | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-95837.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.