medium CVSS 5.5

CVE-2026-47262·Docker vulnerability

containerd is an open-source container runtime. Versions prior to 1.7.33, 2.0.10, 2.1.9, 2.2.5 and 2.3.2, contain a vulnerability that allows a maliciously crafted image to cause a Denial of Service (DoS) condition. When creating a container from this image, memory exhaustion occurs, leading to an Out Of Memory (OOM) kill of the containerd process. This renders the container runtime API unavailable and can disrupt clients such as the Docker Engine or Kubernetes control-plane components. This issue has been fixed in versions 1.7.33, 2.0.10, 2.1.9, 2.2.5 and 2.3.2.

Severity
medium
Software
Docker
Fixed in
2.3.2
Published
2026-07-01

Affected versions

From: 2.3.0

Until: 2.3.2

Fixed in: 2.3.2

How to fix this CVE

Update Docker to version 2.3.2 or later to resolve a memory exhaustion vulnerability in the containerd runtime. This fix prevents maliciously crafted container images from triggering Out of Memory conditions that disable the container daemon. Prioritize this update if you pull images from untrusted sources or run multi-tenant container environments.

sudo dnf update docker-ce containerd

Defensia detects this vulnerability

How to check if you are affected

  1. Run 'docker version' and check the 'containerd version' field; vulnerable versions are 2.3.0 through 2.3.1
  2. Run 'docker info | grep containerd' to confirm containerd is in use and identify its runtime version
  3. Search system logs for OOM killer events: 'sudo dmesg | grep -i oom' or 'journalctl -u docker | grep -i memory'
  4. After patching, re-run 'docker version' and verify containerd version is 2.3.2 or higher

FAQ

What is CVE-2026-47262?

This vulnerability allows attackers to craft a malicious container image that, when instantiated, consumes excessive memory and triggers an OOM killer event that terminates the containerd process. This renders the entire container runtime unavailable to Docker Engine and Kubernetes.

Is CVE-2026-47262 being actively exploited?

No, there is no evidence of active exploitation or public exploits available. However, the low barrier to entry (simple image creation) means organizations should still prioritize patching.

What versions of Docker are affected by CVE-2026-47262?

Docker installations using containerd versions 2.3.0 through 2.3.1 are affected. The vulnerability is fixed in containerd 2.3.2 and later, as well as in versions 1.7.33, 2.0.10, 2.1.9, and 2.2.5.

How do I check if my server is vulnerable to CVE-2026-47262?

Run 'docker version' and look at the 'containerd version' output. If it shows version 2.3.0 or 2.3.1, your system is vulnerable and requires an immediate update.

Does Defensia detect CVE-2026-47262?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Docker is installed on a monitored server, CVE-2026-47262 will appear in your dashboard with remediation steps.

Related Docker CVEs

CVE-2026-42298CVSS 10Postiz is an AI social media scheduling tool. Prior to commit da44801, a "Pwn Request" vulnerability in the Build and Publish PR Docker Image workflow (.github/workflows/pr-docker-build.yml) allows any unauthenticated user to execute arbitrary code during the Docker build process and exfiltrate a highly privileged GITHUB_TOKEN (write-all permissions). This can be achieved simply by opening a Pull Request from a fork with a maliciously modified Dockerfile.dev. This issue has been patched via commit da44801.
CVE-2026-57572CVSS 10Crawl4AI is an open-source LLM-friendly web crawler and scraper. Prior to 0.9.0, the Docker API server accepted request-supplied browser_config.extra_args, which flowed into Chromium's launch arguments. An attacker could inject Chromium switches that replace a child-process launch command together with --no-zygote, causing Chromium to fork or exec an attacker-controlled command as the container's runtime user. The Docker API is unauthenticated by default, so a single request yields arbitrary command execution. This issue is fixed in version 0.9.0.
CVE-2026-26216CVSS 10Crawl4AI versions prior to 0.8.0 contain a remote code execution vulnerability in the Docker API deployment. The /crawl endpoint accepts a hooks parameter containing Python code that is executed using exec(). The __import__ builtin was included in the allowed builtins, allowing unauthenticated remote attackers to import arbitrary modules and execute system commands. Successful exploitation allows full server compromise, including arbitrary command execution, file read and write access, sensitive data exfiltration, and lateral movement within internal networks.
CVE-2026-44181CVSS 10Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions 2.0.0rc2 and above, prior to 3.3.0, the environment variables (KERNEL_XXX) used during the rendering of the Kubernetes manifest are vulnerable to Server Side Template Injection (SSTI). By including Jinja2 template expressions it is possible to execution Python code and OS Commands in the Enterprise Gateway service. The code can use or steal the Kubernetes service account token, which can steal Kubernetes secrets and be used to fully compromise the Kubernetes cluster by scheduling a privileged pod or a pod with a hostPath volume mount. This issue has been fixed in version 3.3.0.
CVE-2026-44182CVSS 10Jupyter Enterprise Gateway launches remote Jupyter Notebook kernels across distributed clusters like Apache Spark, Kubernetes, and Docker Swarm. In versions prior to 3.3.0, the server interpolates untrusted environment variables (e.g., KERNEL_XXX) into Kubernetes manifests without YAML-aware escaping, enabling YAML injection attacks. Attackers can inject new fields, overwrite critical fields (e.g., duplicate securityContext keys, where the last one prevails), and inject document boundaries (--- for new documents, ... for end-of-document) to generate multiple resources, potentially creating arbitrary types, such as privileged pods. The Jinja2 template for the Kubernetes manifest contains several kernel_xxx variables, such as kernel_working_dir that are used when rendering the manifest and are all vectors for YAML injection. This issue has been fixed in version 3.3.0.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-47262. Free for 1 server.

Get started free