# CVE-2026-2270 — Kubernetes

> As of 2026-10-26, CVE-2026-2270 is a MEDIUM-severity vulnerability in Kubernetes, CVSS v3.1 5.9, EPSS 0.3% (27.0th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-2270 as of 2026-10-26; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-26

## What is CVE-2026-2270?

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.

The record classifies CVE-2026-2270 under weakness class [CWE-639](https://intel.threadlinqs.com/cwe/CWE-639). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs high-privilege credentials, needs no user interaction, and has high impact on confidentiality, integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 24 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5.9 — MEDIUM (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **EPSS (FIRST):** 0.3% probability of exploitation in the next 30 days, higher than 27.0% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-26

## Is CVE-2026-2270 being exploited?

It currently carries a trending score of 37 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **Kubernetes**: Kubernetes

## How to fix CVE-2026-2270

No vendor patch reference has been recorded for CVE-2026-2270 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-2270

No threat campaign in the Threadlinqs corpus currently references CVE-2026-2270, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. This product uses the NVD API but is not endorsed or certified by the NVD.

**Mailing list and disclosure**

- [groups.google.com — mailing list](https://groups.google.com/g/kubernetes-security-announce/c/wv0iV-Rcmj4)

**Issue tracking and product pages**

- [github.com — issue tracking](https://github.com/kubernetes/kubernetes/issues/142097)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-2270
No Threadlinqs detection currently covers CVE-2026-2270; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
