# CVE-2025-0426: Node Denial of Service via kubelet Checkpoint API > Attackers can cause Node Denial of Service by filling disk space via unauthenticated kubelet checkpoint requests. - **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 13 Feb 2025 - **Updated:** 13 Feb 2025 - **Also known as:** AZL-56714, CLEANSTART-2026-XP91043, DEBIAN-CVE-2025-0426, GHSA-jgfp-53c3-624w, GO-2025-3465, MINI-2rrx-986v-j839, MINI-rw7x-qp73-wv5p, MINI-xf4v-mxxf-gvhw, MINI-xh3c-rx24-fxrx, OESA-2025-1259, OESA-2025-1273, openSUSE-SU-2025:14816-1, openSUSE-SU-2025:14817-1, openSUSE-SU-2025:14818-1, openSUSE-SU-2025:14819-1 ## What is CVE-2025-0426? CVE-2025-0426 is a medium-severity denial of service vulnerability in Kubernetes kubelet, published on 13 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A security issue was discovered in Kubernetes where a large number of container checkpoint requests made to the unauthenticated kubelet read-only HTTP endpoint may cause a Node Denial of Service by filling the Node's disk. Weakness: CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2025-0426? 9 open source packages ship an affected version, including k8s.io/kubernetes. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `k8s.io/kubernetes` | Go | All versions | 1.29.14, 1.30.10, 1.31.6, 1.32.2 | | `k8s.io/kubernetes` | Go | All versions | 1.29.14 | | `k8s.io/kubernetes` | Go | All versions | 1.29.14 | | `k8s.io/kubernetes` | Go | From 1.30.0 | 1.30.10 | | `k8s.io/kubernetes` | Go | From 1.30.0 | 1.30.10 | | `k8s.io/kubernetes` | Go | From 1.31.0 | 1.31.6 | | `k8s.io/kubernetes` | Go | From 1.31.0 | 1.31.6 | | `k8s.io/kubernetes` | Go | From 1.32.0 | 1.32.2 | | `k8s.io/kubernetes` | Go | From 1.32.0 | 1.32.2 | | `kubernetes1.29` | openSUSE:Tumbleweed | All versions | 1.29.14-1.1 | | `kubernetes1.30` | openSUSE:Tumbleweed | All versions | 1.30.10-1.1 | | `kubernetes1.31` | openSUSE:Tumbleweed | All versions | 1.31.6-1.1 | | `kubernetes1.32` | openSUSE:Tumbleweed | All versions | 1.32.2-1.1 | ## How do I fix CVE-2025-0426? Upgrade k8s.io/kubernetes to a fixed version for your release line: 1.29.14, 1.30.10, 1.31.6 or 1.32.2. ## Is CVE-2025-0426 being exploited? There is no known exploitation of CVE-2025-0426 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-0426 and fix it if it is affected. What it is: CVE-2025-0426 is a medium-severity denial of service vulnerability in Kubernetes kubelet, published on 13 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-0426 in the wild and no public exploit code. Affected packages and fixed versions: - k8s.io/kubernetes (Go): affected all versions; fixed in 1.29.14, 1.30.10, 1.31.6, 1.32.2 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.29.14 - k8s.io/kubernetes (Go): affected all versions; fixed in 1.29.14 - k8s.io/kubernetes (Go): affected from 1.30.0; fixed in 1.30.10 - k8s.io/kubernetes (Go): affected from 1.30.0; fixed in 1.30.10 - k8s.io/kubernetes (Go): affected from 1.31.0; fixed in 1.31.6 - k8s.io/kubernetes (Go): affected from 1.31.0; fixed in 1.31.6 - k8s.io/kubernetes (Go): affected from 1.32.0; fixed in 1.32.2 - k8s.io/kubernetes (Go): affected from 1.32.0; fixed in 1.32.2 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-0426/ (Markdown: https://insights.sbomify.com/CVE-2025-0426/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-0426 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-0426 - OSV: https://osv.dev/vulnerability/CVE-2025-0426 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-0426/ Summaries are generated and may contain mistakes; the official description above is the record.