Bug 2457729 (CVE-2026-35469)

Summary: CVE-2026-35469 Kubelet: CRI-O: kube-apiserver: Kubelet, CRI-O, kube-apiserver: Denial of Service via SPDY streaming code
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: unspecifiedCC: alcohan, anjoseph, dfreiber, drow, fdeutsch, gparvin, jbalunas, jburrell, jprabhak, manissin, mwringe, oramraz, pahickey, rhaigner, sakbas, security-response-team, smullick, stirabos, thason, vkumar, wtam
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the SPDY streaming code used by Kubelet, CRI-O, and kube-apiserver. An attacker with specific cluster roles, such as those allowing access to pod port forwarding, execution, or attachment, or node proxying, could exploit this vulnerability. This could lead to a Denial of Service (DoS) by causing the affected components to become unresponsive.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2467585, 2467586, 2467587, 2467588, 2467589, 2467594, 2467595, 2467596, 2467597, 2467598, 2467600, 2467601, 2467602, 2467603, 2467590, 2467591, 2467592, 2467593, 2467599, 2467604, 2467605, 2467606    
Bug Blocks:    
Deadline: 2026-04-13   

Description OSIDB Bzimport 2026-04-13 03:53:46 UTC
Summary:
Possible DOS in SPDY streaming code, used for attach, exec and port forwarding.

Requirements To Exploit:
Access to the kubelet's endpoint (granted through nodes/proxy) or access to any of portforward, exec, or attach to pods. These all can be represented by the cluster roles

pods/portforward (create)

pods/exec (create)

pods/attach (create)

nodes/proxy (get/create)

Component Affected:
Kubelet, CRI-O, kube-apiserver

Version Affected:
Openshift 4.21.4 and below

Patch Available:
yes

Version Fixed:
none yet

Cvss:
(Based on [_https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator_]). Please note that only the Base Score Metrics are required by the incident response team.

Impact:
Based on the https://access.redhat.com/security/updates/classification , what do you think would be the impact and why? This helps a lot the analyst to understand why such a report must be or not considered Moderate/Important or even Critical.

Steps To Reproduce:
apply:

```

—
apiVersion: v1
kind: ServiceAccount
metadata:
name: poc-sa-portforward
namespace: default
—
apiVersion: [rbac.authorization.k8s.io/v1:(http://rbac.authorization.k8s.io/v1)(http://rbac.authorization.k8s.io/v1)]
kind: Role
metadata:
name: poc-role-portforward
namespace: default
rules:

apiGroups: [""]
 resources: ["pods/portforward"]
 verbs: ["create"]
—
apiVersion: [rbac.authorization.k8s.io/v1:(http://rbac.authorization.k8s.io/v1)(http://rbac.authorization.k8s.io/v1)]
kind: RoleBinding
metadata:
 name: poc-rb-portforward
 namespace: default
subjects:

kind: ServiceAccount
 name: poc-sa-portforward
 namespace: default
roleRef:
 kind: Role
 name: poc-role-portforward
 apiGroup: [rbac.authorization.k8s.io](http://rbac.authorization.k8s.io/)
—
apiVersion: v1
kind: Pod
metadata:
 name: poc-target
 namespace: default
spec:
 containers:

name: nginx
 image: nginx:alpine

```

set env:

```

export API_SERVER=$(kubectl config view --minify -o jsonpath='{.clusters[0].cluster.server}' | sed 's|https://||')

export TOKEN=$(kubectl create token poc-sa-portforward)

export POD=poc-target

```

run attached poc_portforward.py

Mitigation:
disable the above cluster roles from untrusted users.

Embargo Reason:
Coordination with three upstream communities: containerd, CRI-O, kubernetes

Original Report:
https://github.com/moby/spdystream/security/advisories/GHSA-pc3f-x583-g7j2

Comment 4 errata-xmlrpc 2026-07-08 15:50:43 UTC
This issue has been addressed in the following products:

  RHEM 1.0 for RHEL 9

Via RHSA-2026:36796 https://access.redhat.com/errata/RHSA-2026:36796

Comment 5 errata-xmlrpc 2026-07-09 13:55:29 UTC
This issue has been addressed in the following products:

  Red Hat OpenShift Container Platform 4.19

Via RHSA-2026:34755 https://access.redhat.com/errata/RHSA-2026:34755

Comment 6 errata-xmlrpc 2026-07-16 14:32:29 UTC
This issue has been addressed in the following products:

  RHEM 1.1 for RHEL 10
  RHEM 1.1 for RHEL 9

Via RHSA-2026:41019 https://access.redhat.com/errata/RHSA-2026:41019