# CVE-2026-2270: StatefulSet and ControllerRevision write permissions allow cross-namespace pod creation


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** AZL-111140, DEBIAN-CVE-2026-2270, GHSA-3jhc-p65m-8464

## What is CVE-2026-2270?

CVE-2026-2270 is a medium-severity vulnerability in Kubernetes, published on 26 Oct 2026. 

### Official description

A confused deputy attack exists in the StatefulSet controller that allows a user with namespace-scoped write permissions on StatefulSet and ControllerRevision objects to create a cross-namespace pod. An attacker exploiting this vulnerability would have full control over the resulting pod’s metadata and specification, including namespace selection. Note that the cross-namespace pod will be immediately deleted by the garbage collector unless the attacker is able to construct a valid StatefulSet OwnerReference. This would require referencing the UID of an existing StatefulSet in the victim’s namespace.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-2270?


## How do I fix CVE-2026-2270?

Upgrade to a fixed version.

## Is CVE-2026-2270 being exploited?

There is no known exploitation of CVE-2026-2270 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2270 and fix it if it is affected.

What it is: CVE-2026-2270 is a medium-severity vulnerability in Kubernetes, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-2270 in the wild and no public exploit code.

Affected product: Kubernetes. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2270/ (Markdown: https://insights.sbomify.com/CVE-2026-2270/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2270
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2270
- OSV: https://osv.dev/vulnerability/CVE-2026-2270

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2270/
Summaries are generated and may contain mistakes; the official description above is the record.