OpenShift 4.22.11 addresses CRI-O passwd injection and Go traversal flaws
Red Hat rates the asynchronous update Important and advises all OpenShift 4.22 users to install its updated packages and images.
Red Hat has released OpenShift Container Platform 4.22.11 as an asynchronous security and bug-fix update, rating the security impact Important and advising all 4.22 users to upgrade when the release reaches their update channel. The update is split between an RPM package advisory and a container-image advisory.
Three named package-level fixes
The RPM advisory names three security fixes. One addresses a CRI-O bypass of an earlier fix that could allow /etc/passwd injection through the HOME environment variable (CVE-2026-15809). A second fixes directory traversal caused by symlink following in Go's os.Root implementation (CVE-2026-39822). The third addresses denial of service from a maliciously crafted MIME header in Go's MIME handling (CVE-2026-42504), according to RHSA-2026:57361.
Red Hat's companion image advisory carries the updated OpenShift release images for x86_64, s390x, ppc64le and aarch64. It also lists additional CVEs covered by the image update and a set of bug fixes, including a PinnedImageSet condition that could become stuck, an Azure Disk CSI controller crash, excessive creation of per-user console-settings ConfigMaps and kube-apiserver thread exhaustion in a FIPS-mode scenario.
What administrators should do
Red Hat says administrators can check for 4.22.11 through the OpenShift web console or with the oc command-line tool once the update is available in the appropriate release channel. Applying the update requires both the package and image components described by the paired advisories; the RPM advisory explicitly directs all OpenShift 4.22 users to move to the updated packages and images.
The practical takeaway is straightforward: this is not merely a routine patch-level rollup. Red Hat has attached an Important security rating, identified three package-level vulnerabilities by name and coupled those fixes with updated cluster images. Operators should review the advisories against their 4.22 estates and schedule the update through their normal cluster-change process.
sources
comments · 0