# Kubernetes v1.35.9

2026-09-23 · [Original release notes](https://github.com/kubernetes/kubernetes/releases/tag/v1.35.9) · [Full summary](https://ratatosk.io/en/releases/kubernetes/v1.35.9)

Security 4 · Breaking changes 1 · Deprecations 1 · Important fixes 2 · Dependency updates 2 · Other changes 3

## Security (4)

### [medium] Windows `kubectl cp` arbitrary-path write fixed

- Affects: Not stated in the release notes
- [CVE-2026-19444](https://github.com/kubernetes/kubernetes/issues/141294)

When an attacker controls the source container, malicious archive paths could escape the intended destination and write files anywhere allowed by the local user's system permissions. After the upgrade, those paths can no longer escape the destination.

Security advisory:

> A path traversal vulnerability exists in the `kubectl cp` command when it is run on Windows. `kubectl cp` copies files between containers and the user machine. To copy files *from* a container, Kubernetes runs `tar` inside the container to create a tar archive, copies it over the network, and `kubectl` unpacks it on the user's machine. If the `tar` binary in the container is malicious, it could run any code and output unexpected, malicious results.
> An attacker who controls the contents of a container could use this to write files to arbitrary paths on the user's machine when `kubectl cp` is called, limited only by the system permissions of the local user. This issue only affects clients on Windows platforms.
> You are affected if you run the `kubectl` client on Windows and use `kubectl cp` to copy files *from* a container whose contents you do not fully control.
> Prior to upgrading, this vulnerability can be mitigated by only copying files from containers you trust, or by avoiding `kubectl cp` from untrusted containers on Windows.

https://github.com/kubernetes/kubernetes/issues/141294

Security advisory:

> kubectl cp path traversal on Windows allows arbitrary file writes

https://github.com/kubernetes/kubernetes/issues/141294

### [medium] StatefulSet cross-namespace pod creation vulnerability fixed

- Affects: Not stated in the release notes
- [CVE-2026-2270](https://github.com/kubernetes/kubernetes/issues/142097)

An attacker with namespace-scoped write access to `StatefulSet` and `ControllerRevision` objects could create a pod in another namespace and control its metadata and specification. The pod was deleted unless it had a valid `StatefulSet` OwnerReference to an existing StatefulSet in the victim’s namespace; fixed versions restore only the `spec` field from ControllerRevisions.

Security advisory:

> 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.
> This issue can be mitigated by upgrading to a fixed kube-controller-manager version. The fixed versions are patched to ensure that only the spec field in StatefulSets will be restored from ControllerRevisions.

https://github.com/kubernetes/kubernetes/issues/142097

Security advisory:

> StatefulSet and ControllerRevision write permissions allow cross-namespace pod creation

https://github.com/kubernetes/kubernetes/issues/142097

### [medium] Windows kubelet UNC symlink vulnerability fixed

- Affects: Not stated in the release notes
- [CVE-2026-76654](https://github.com/kubernetes/kubernetes/issues/142098)

When a pod's `volumeMount` `subPath` was a symlink to an attacker-controlled network share at a UNC path, kubelet attempted NTLM authentication, exposing the NetNTLMv2 hash of the account running kubelet. Fixed versions refuse UNC symlink targets on Windows.

Security advisory:

> CVSS Rating: [CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N](https://www.first.org/cvss/calculator/3.1#CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:N/A:N) - Medium (5.8)
> An NTLM coercion vulnerability exists on Windows nodes when the subPath supplied in a pod's volumeMounts is set to a symbolic link that points to an attacker-controlled network share. When a kubelet resolves symlinks, it does not reject a target that resolves to a UNC path. As a result, the kubelet will transparently attempt to authenticate to the share using NTLM.
> This allows an attacker to obtain the NetNTLMv2 hash of the account under which the kubelet is running. An attacker could then attempt to crack the hash to retrieve the corresponding password or relay it to impersonate the node, if the node is domain-joined.
> This issue can be mitigated by upgrading to a fixed kubelet version. The fixed versions update kubelet to refuse UNC symlink targets on Windows.

https://github.com/kubernetes/kubernetes/issues/142098

Security advisory:

> Subpath symlinking on Windows nodes permits NTLM coercion

https://github.com/kubernetes/kubernetes/issues/142098

### DRA allocator rejects over-limit `ResourceClaim` requests

- Affects: DRA allocation for `ResourceClaim`s in kube-scheduler (Inferred)

When device request counts exceeded the per-claim limit, an overflow in the native `int` total could bypass the check and crash kube-scheduler while allocating the result slice.

> - Kube-scheduler: a ResourceClaim whose device request counts add up past the int range no longer crashes the scheduler or skips the `firstAvailable` fallback in the DRA allocator. A request over the per-claim device limit is rejected with an error naming it, and an oversized `firstAvailable` alternative falls through to a smaller one. ([#141924](https://github.com/kubernetes/kubernetes/pull/141924), [@thc1006](https://github.com/thc1006)) [SIG Node]

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.md

## Breaking changes (1)

### Kubelet fallback metric version label updated

- Affects: kubelet setups using CRI implementations without `RuntimeConfig` support (Inferred)

When kubelet falls back to `cgroupDriver` from its config in this situation, `CRILosingSupport` used the `version` label value `1.36.0`; it now uses `1.38.0`.

Evidence: “kubeletmetrics.CRILosingSupport.WithLabelValues("1.38.0").Inc()” https://github.com/kubernetes/kubernetes/pull/139268

> - Kubelet: defer the configurations flags (and the related fallback behavior) deprecation removal timeline from 1.37 to 1.38 to align with containerd v1.7 support

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.md

## Deprecations (1)

### kubeadm `cgroupDriver` fallback removal warning moved to 1.38

- Affects: kubeadm `ContainerRuntimeVersion` preflight checks with runtimes that lack `RuntimeConfig`
- Removed in: 1.38

Previously, the warning placed fallback removal in 1.36. In these setups, kubelet versions older than 1.38 now receive a preflight warning.

>   kubeadm: the preflight check `ContainerRuntimeVersion` validates if the installed container runtime supports the `RuntimeConfig` gRPC method. For older kubelet versions than 1.38, it will return a preflight warning. ([#139268](https://github.com/kubernetes/kubernetes/pull/139268), [@carlory](https://github.com/carlory)) [SIG Cluster Lifecycle, Node and Testing]

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.md

## Important fixes (2)

### DRA allocator fallback from oversized alternatives fixed

- Affects: DRA allocator use with `ResourceClaim` `firstAvailable` alternatives (Inferred)

When an oversized `firstAvailable` alternative preceded a smaller one, the allocator could skip the smaller fallback. It can now prune the oversized alternative and select the smaller one.

> - Kube-scheduler: a ResourceClaim whose device request counts add up past the int range no longer crashes the scheduler or skips the `firstAvailable` fallback in the DRA allocator. A request over the per-claim device limit is rejected with an error naming it, and an oversized `firstAvailable` alternative falls through to a smaller one. ([#141924](https://github.com/kubernetes/kubernetes/pull/141924), [@thc1006](https://github.com/thc1006)) [SIG Node]

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.md

### `kubeadm init` keeps node-specific resolver paths out of shared kubelet config

- Affects: setups using systemd-resolved with `kubeadm init` (Inferred)

> - Kubeadm: no longer persists a node-specific systemd-resolved resolvConf path in the cluster-wide kubelet-config ConfigMap during init. ([#141629](https://github.com/kubernetes/kubernetes/pull/141629), [@HirazawaUi](https://github.com/HirazawaUi)) [SIG Cluster Lifecycle]

https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.35.md

## Dependency updates (2)

2 more, none mentioning security

- `- Kubernetes is now built using Go 1.26.8 ([#142182](https://github.com/kubernetes/kubernetes/pull/142182), [@cpanato](https://github.com/cpanato)) [SIG Release and Testing]`
- `- Kubernetes is now built using Go 1.26.8 ([#142182](https://github.com/kubernetes/kubernetes/pull/142182), [@cpanato](https://github.com/cpanato)) [SIG Release and Testing]`

## Other changes (3)

- Kubelet configuration flag and fallback removal deferred to 1.38
- Three tests demoted from conformance to regular e2e
- Three in-place Pod Resize tests moved from conformance to regular e2e

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
