All Threat Alerts
criticalOSINT Alert

Kubernetes v1.36: In-Place Vertical Scaling for Pod-Level Resources Graduates to Beta

Following the graduation of Pod-Level Resources to Beta in v1.34 and the General Availability (GA) of In-Place Pod Vertical Scaling in v1.35, the Kubernetes community is thrilled to announce that In-Place Pod-Level Resources Vertical Scaling has graduated to Beta in v1.36! This feature is now enabled by default via the InPlacePodLevelResourcesVerticalScaling feature gate. It allows users to update the aggregate Pod resource budget (.spec.resources) for a running Pod, often without requiring a co

Friday, May 1, 2026LinuxVulnios Threat Intelligence
Share:

Vulnerability Snapshot

This advisory is rated CRITICAL โ€” exploitation is trivial or already observed in the wild and impact is severe. Patch immediately, not on the next maintenance window.

Affected technology: Kubernetes, containerd.

Executive Summary

Following the graduation of Pod-Level Resources to Beta in v1.34 and the General Availability (GA) of In-Place Pod Vertical Scaling in v1.35, the Kubernetes community is thrilled to announce that In-Place Pod-Level Resources Vertical Scaling has graduated to Beta in v1.36! This feature is now enabled by default via the InPlacePodLevelResourcesVerticalScaling feature gate. It allows users to update the aggregate Pod resource budget (.spec.resources) for a running Pod, often without requiring a co

Source

AI Security Advisor

Powered by Gemini

Get AI-powered security recommendations tailored to this specific threat โ€” including risk assessment, detection guidance, MITRE ATT&CK mapping, and actionable remediation steps.

Affected Products

Kubernetescontainerd

Related Threat Alerts

Frequently Asked Questions

What is "Kubernetes v1.36: In-Place Vertical Scaling for Pod-Level Resources Graduates to Beta"?

This is a critical-severity osint alert from Kubernetes Blog. It covers Kubernetes, containerd and was flagged for security teams to evaluate.

Am I affected?

Check whether your environment runs Kubernetes, containerd. If you operate any of those, treat yourself as in scope until you have evidence otherwise. A Vulnios scan will identify the exact assets carrying the affected version.

How urgent is the response?

Critical: do not wait for your normal patch cycle. Verify exposure today, apply the vendor patch immediately, and add detection rules for any post-exploit indicators.

How do I remediate?

Apply the vendor patch listed in the upstream advisory linked under Sources. If the patch is not yet available, follow the vendor-supplied workaround (often a config flag or feature disable) and add detections for the published exploit pattern in your SIEM. Re-scan after the patch lands to confirm the finding clears.

How does Vulnios help with this?

Vulnios continuously cross-references your asset inventory against the live CVE feed (NVD, vendor advisories, CISA KEV, and curated OSINT). When a new CVE matches your environment, you get a prioritized finding with the severity, KEV status, exploit-prediction (EPSS), and a direct path to the vendor patch. You can start a free scan from the homepage.

kubernetescloudcontainerrceics-otmalwareconflictinfrastructureLinuxKubernetesSlack

Protect Your Organization

Monitor CVEs, scan for vulnerabilities, and get real-time threat alerts โ€” all in one platform.

Get instant alerts on Telegram

Join our public channel for real-time critical CVE alerts.

Follow @vulnios