Kubernetes v1.37: Static Pods restricted from referencing Secrets/ConfigMaps and bypass via feature-gates

Based on the provided webpage screenshot, here is a summary of the key information regarding the vulnerability: Vulnerability Overview Vulnerability Name: Static Pods can no longer reference Secrets or ConfigMaps Description: In Kubernetes v1.37, Static Pods are no longer allowed to directly reference Secrets or ConfigMaps. This change was implemented to fix a bug that allowed Static Pods to access these resources directly via the API server, which was unintended behavior. Scope of Impact Affected Components: Static Pod functionality in Kubernetes v1.37 and later versions. Specific Impact: Static Pods will no longer be able to directly reference Secrets or ConfigMaps, which may affect Static Pod configurations that rely on these resources. Remediation Plan Fix Measure: In Kubernetes v1.37, references to Secrets and ConfigMaps from Static Pods are strictly prohibited. Temporary Solution: If you need to continue using these references in v1.37, you can temporarily disable this restriction by setting . Long-term Solution: Users are advised to migrate to using the API server to manage Secrets and ConfigMaps to ensure security and stability. POC Code or Exploit Code Code Example: Additional Relevant Information Related Documentation: Refer to the Static Pods section in the official Kubernetes documentation to learn about the configuration and management of Static Pods. Community Discussion: You can view related Issues and PRs in the Kubernetes GitHub repository to understand the discussions and background surrounding this change. The above summary covers the vulnerability overview, scope of impact, remediation plan, as well as relevant code examples and documentation links.

Goal Reached Thanks to every supporter — we hit 100%!

Kubernetes v1.37: Static Pods restricted from referencing Secrets/ConfigMaps and bypass via feature-gates