CVE-2025-0426 — kubernetes
MEDIUMCVE-2025-0426 is a medium-severity (CVSS 6.2) Uncontrolled Resource Consumption vulnerability in k8s.io/kubernetes. A fix is available for k8s.io/kubernetes — see the affected versions and patch details below.
Node Denial of Service via kubelet Checkpoint API
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-0426.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-0426 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
k8s.io/kubernetes🐹k8s.io/kubernetes🐹k8s.io/kubernetes🐹k8s.io/kubernetesReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | k8s.io/kubernetes | ≥ 1.32.0&&< 1.32.2 | 1.32.2go get k8s.io/kubernetes@v1.32.2 |
| 🐹Go | k8s.io/kubernetes | ≥ 1.31.0&&< 1.31.6 | 1.31.6go get k8s.io/kubernetes@v1.31.6 |
| 🐹Go | k8s.io/kubernetes | ≥ 1.30.0&&< 1.30.10 | 1.30.10go get k8s.io/kubernetes@v1.30.10 |
| 🐹Go | k8s.io/kubernetes | all versions | 1.29.14go get k8s.io/kubernetes@v1.29.14 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for k8s.io/kubernetes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update k8s.io/kubernetes to 1.32.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-0426 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-0426 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-0426. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
OpenShift is not impacted by this vulnerability since the kubelet's unauthenticated read-only port is not enabled in that product.
| Product | Fixed in | Advisory |
|---|---|---|
| RHODF-4.17-RHEL-9 | odf4/cephcsi-rhel9:v4.17.5-2 | RHSA-2025:1824 |
| RHODF-4.18-RHEL-9 | odf4/cephcsi-rhel9:v4.18.0-54 | RHSA-2025:2652 |
Frequently Asked Questions
Is CVE-2025-0426 in your dependencies?
O3 Security finds CVE-2025-0426 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.