CVE-2025-0426 is an uncontrolled resource-consumption vulnerability in the Kubernetes kubelet Container Checkpoint API. In affected kubelet versions, the checkpoint API is reachable through the unauthenticated kubelet read-only HTTP endpoint. An attacker can submit numerous container checkpoint requests, causing checkpoint data to consume available node disk capacity and resulting in a node-level denial-of-service condition.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Kubernetes kubelet vulnerability permitting denial of service on a node through the kubelet checkpoint API, fixed in the update.
Kubernetes kubelet node-denial-of-service vulnerability via the kubelet checkpoint API.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.