After compromising one node, patch other nodes with NoSchedule/NoExecute taints
Sensitive pods are forced to reschedule onto the compromised node
Stealing their tokens or intercepting traffic is a separate step needing its own access on the compromised node (secrets read, exec, or hostNetwork).
Tainting only performs the steering
Note:
CVE-2025-5187 (fixed 1.33.4) was a NodeRestriction bypass and applies only to a compromised kubelet identity, not to an RBAC patch grant.
Confirmed still working on 1.36.1 with patch on nodes alone, so treat this path as unpatched.