# CVE-2025-47290: Containerd vulnerable to host filesystem access during image unpack


- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:U`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 20 May 2025
- **Updated:** 20 May 2025
- **Also known as:** BELL-CVE-2025-47290, GHSA-cm76-qm8v-3j95, GO-2025-3699, MINI-65jq-g62h-p52c, openSUSE-SU-2025:15146-1

## What is CVE-2025-47290?

CVE-2025-47290 is a high-severity vulnerability in containerd, published on 20 May 2025. 

### Official description

containerd is a container runtime. A time-of-check to time-of-use (TOCTOU) vulnerability was found in containerd v2.1.0. While unpacking an image during an image pull, specially crafted container images could arbitrarily modify the host file system. The only affected version of containerd is 2.1.0.  Other versions of containerd are not affected. This bug has been fixed in containerd 2.1.1. Users should update to this version to resolve the issue. As a workaround, ensure that only trusted images are used and that only trusted users have permissions to import images.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2025-47290?

3 open source packages ship an affected version, including github.com/containerd/containerd/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/containerd/containerd/v2` | Go | From 2.1.0 | 2.1.1 |
| `github.com/containerd/containerd/v2` | Go | From 2.1.0 | 2.1.1 |
| `github.com/containerd/containerd/v2` | Go | From 2.1.0 | 2.1.1 |
| `kind` | openSUSE:Tumbleweed | All versions | 0.29.0-1.1 |

Products: Linuxfoundation Containerd.

## How do I fix CVE-2025-47290?

Upgrade github.com/containerd/containerd/v2 to 2.1.1 or later.

## Is CVE-2025-47290 being exploited?

There is no known exploitation of CVE-2025-47290 in the wild and no public exploit code.

## Other vulnerabilities in containerd

- [CVE-2026-53488](https://insights.sbomify.com/CVE-2026-53488/): containerd CRI — image-config `LABEL` flows to restart-monitor `binary://` logger: host-root command execution from an image pull (critical 9.4)
- [CVE-2026-53492](https://insights.sbomify.com/CVE-2026-53492/): containerd CRI checkpoint restore CDI annotation smuggling (high 8.4)
- [CVE-2026-53489](https://insights.sbomify.com/CVE-2026-53489/): containerd: Arbitrary host CRI log file read via symlink following in CRI checkpoint restore (high 8.2)
- [CVE-2026-46680](https://insights.sbomify.com/CVE-2026-46680/): containerd user ID handling bypass allows runAsNonRoot evasion (high 7.3)
- [CVE-2024-25621](https://insights.sbomify.com/CVE-2024-25621/): containerd affected by a local privilege escalation via wide permissions on CRI directory (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47290 and fix it if it is affected.

What it is: CVE-2025-47290 is a high-severity vulnerability in containerd, published on 20 May 2025. 
Exploitation: There is no known exploitation of CVE-2025-47290 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/containerd/containerd/v2 (Go): affected from 2.1.0; fixed in 2.1.1
- github.com/containerd/containerd/v2 (Go): affected from 2.1.0; fixed in 2.1.1
- github.com/containerd/containerd/v2 (Go): affected from 2.1.0; fixed in 2.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-47290/ (Markdown: https://insights.sbomify.com/CVE-2025-47290/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47290
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47290
- OSV: https://osv.dev/vulnerability/CVE-2025-47290

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-47290/
Summaries are generated and may contain mistakes; the official description above is the record.