Container image patching
Container images are patched by rebuilding and redeploying, not by changing a running container. NIST SP 800-190 says a container needing an upgrade “is simply destroyed and replaced.” Kubernetes ships patch releases monthly, next on 15 Dec 2026, and supports each series about 14 months. Read 19 Nov 2026.
What replaces the install step
NIST SP 800-190 describes containers as stateless entities that are “deployed but not changed”: when contents must change, the container is destroyed and replaced with a new one. It follows that “all vulnerability management, including patches and configuration settings, is typically taken care of by the developer when building a new image version,” which shifts responsibility from operations to developers and calls for coordination between them (NIST SP 800-190). The policy hook is a maximum age for an image or its base layer, and a rebuild trigger when the base publisher releases a fix.
Docker's guidance says the same in practical terms: an image is a snapshot, including every base image and library, so rebuild regularly. A tag such as the ubuntu 24.04 tag may resolve to a newer underlying image over time as the publisher rebuilds it with security patches; the build flag --pull makes the builder check for and download a newer base image even if one is cached, and --no-cache re-runs all steps, so the two are used together for a fresh build (Docker build guidance, listed in the sources below).
The image rebuild belongs to the deploy step; the hosts follow the Linux server window.
The orchestrator is also software
| Kubernetes series | Maintenance mode | End of life |
|---|---|---|
| 1.36 | 28 Apr 2027 | 28 Jun 2027 |
| 1.37 | 28 Aug 2027 | 28 Oct 2027 |
Kubernetes says its typical patch cadence is monthly, a bit faster (one to two weeks) after a new minor release, with critical fixes allowed outside the cadence. Upcoming targets on the page are 15 Dec 2026 and 12 Jan 2027. Each series gets roughly fourteen months: twelve standard, then two in maintenance mode, where extra releases may fix CVE-assigned vulnerabilities, dependency issues including base image updates, and critical core problems (Kubernetes). The consequence is a cluster-version deadline in the policy, not only an image rule.
Where live patching stops
Microsoft's hotpatch for Windows Server does not apply to container images: its page states that “Windows Server container base images” are not supported. Container hosts can be hotpatched; the images still need rebuilding. See systems that cannot reboot.
Window, rollback and evidence
- Window: images rebuilt on the base publisher's release, deployed through the normal pipeline; hosts patched on the Linux or Windows windows.
- Rollback: redeploy the previous immutable image version; keep the last known good version tagged.
- NIST adds that remote shells should never be enabled inside containers, so the fix path stays a redeploy.
- Evidence: image build date and base image digest per workload, the inventory of running image versions, and the cluster version.
Sources
- NIST SP 800-190, Application Container Security Guide, read 19 Nov 2026
- Docker Docs, Building guidance, rebuild your images often, read 19 Nov 2026
- Kubernetes, Patch Releases, read 19 Nov 2026
- Microsoft Learn, Hotpatch for Windows Server, read 19 Nov 2026
Last reviewed 19 Nov 2026