RHSA-2026:35111HighCVSS 8.8

Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update

Published
July 2, 2026
Last Modified
August 20, 2026

🔗 CVE IDs covered (7)

CVE-2026-44740 →CVE-2026-46680 →CVE-2026-47262 →CVE-2026-50195 →CVE-2026-53488 →CVE-2026-32285 →CVE-2026-41506 →

📋 Description

CVE-2026-32285 — github.com/buger/jsonparser: github.com/buger/jsonparser: Denial of Service via malformed JSON input CVE-2026-41506 — golang: github.com/go-git/go-git: go-git: Information disclosure of HTTP authentication credentials via redirects CVE-2026-44740 — github.com/go-git/go-billy: Billy: Denial of Service via crafted input due to insufficient validation CVE-2026-46680 — github.com/containerd/containerd: containerd: Privilege escalation via incorrect user ID handling CVE-2026-47262 — github.com/containerd/containerd: containerd: Denial of Service via maliciously crafted image leading to unbounded group parsing CVE-2026-50195 — github.com/containerd/containerd: containerd: Arbitrary code execution via CRI checkpoint image tag poisoning CVE-2026-53488 — github.com/containerd/containerd: containerd: Host-root command execution via unvalidated image config labels in CRI plugin

🎯 Affected products4

  • Red Hat Hardened Images
  • trivy-main@aarch64 as a component of Red Hat Hardened Images
  • trivy-main@src as a component of Red Hat Hardened Images
  • trivy-main@x86_64 as a component of Red Hat Hardened Images

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/ Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability. Workaround: To mitigate the issue, we suggest upgrading to versions 5.9.0+ or 6.0.0-alpha.1+ Workaround: Enforce a specific numeric runAsUser in the Kubernetes Pod securityContext, which overrides the User directive in the container image and prevents the bypass. Additionally, restrict access to push container images to trusted users only, and validate image provenance before deployment. Workaround: No mitigation is needed for Red Hat products. The vulnerable code path in containerd's CRI plugin group-parsing logic is not executed because Red Hat uses CRI-O as the container runtime. Products that bundle containerd as a library dependency for OCI image operations are not affected. Workaround: No mitigation is needed as the vulnerable code is not present in the containerd versions shipped in Red Hat products. Workaround: Restrict container image pulls to trusted registries using admission policies or image signature verification. Where containerd is used as the container runtime, disable or restrict the binary:// logger URI scheme in the containerd configuration to prevent the label-to-logger attack path.

🔗 References (11)