Skip to main content
CVE-2026-2270VulnerabilityPublished

Confused Deputy Attack Exists

Source GCVE Database

0
Authoritative record:CVE-2026-2270· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium.

Data as of 27 Oct 2026, 02:12 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
KubernetesKubernetesAffected
  • >=1.34.0 <=1.34.11
  • >=1.35.0 <=1.35.8
  • >=1.36.0 <=1.36.4
  • >=1.37.0 <=1.37.0
Fixed in–
GitHubkubernetes/kubernetespkg:github/kubernetes/kubernetesOther threatsAffected
  • >=1.34.0 <=1.34.11
  • >=1.35.0 <=1.35.8
  • >=1.36.0 <=1.36.4
  • >=1.37.0 <=1.37.0
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.

References

Community reviews

Loading reviews…