Loading vulnerability…
CVE-2026-2270 is a confused-deputy vulnerability in the StatefulSet controller within Kubernetes kube-controller-manager. During restoration from a ControllerRevision, the controller could restore attacker-controlled fields beyond the StatefulSet specification. A user with write permissions to both StatefulSets and ControllerRevisions in one namespace could thereby cause the more privileged controller to create a pod in another namespace, controlling its metadata and specification. Kubernetes garbage collection normally deletes the resulting pod unless it has a valid StatefulSet OwnerReference in the target namespace. Affected releases are 1.34.11 and earlier in the 1.34 branch, 1.35.8 and earlier in the 1.35 branch, 1.36.4 and earlier in the 1.36 branch, and 1.37.0.
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.
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.