Confused Deputy Attack Exists
Source GCVE Database
Not known to be exploited · CVSS 5.9 Medium.
Data as of 27 Oct 2026, 02:12 UTC
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| KubernetesKubernetes | Affected
| Fixed in– |
GitHubkubernetes/kubernetespkg:github/kubernetes/kubernetesOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Since the vulnerability requires namespace-scoped write permissions on StatefulSet and ControllerRevision objects, restricting such permissions to trusted users can mitigate risk. Monitor vendor advisories for official patches or updates. Until a fix is available, limit write access to StatefulSet and ControllerRevision resources and audit usage carefully.
Description
CVE-2026-2270 is a medium severity vulnerability in the StatefulSet controller that enables a confused deputy attack. A user with namespace-scoped write permissions on StatefulSet and ControllerRevision objects can create a pod in a different namespace. The attacker gains full control over the pod's metadata and specification, including the namespace. However, the cross-namespace pod is deleted by the garbage collector unless the attacker can reference a valid StatefulSet OwnerReference in the victim namespace.