RHSA-2026:95365CriticalCVSS 8.2

Red Hat Security Advisory: Red Hat Cost Management On-Premise container image update

Published
November 4, 2026
Last Modified
November 12, 2026

🔗 CVE IDs covered (14)

CVE-2026-53615 →CVE-2026-76642 →CVE-2026-77214 →CVE-2026-97687 →CVE-2026-102633 →CVE-2026-53612 →CVE-2026-53614 →CVE-2026-78408 →CVE-2026-78410 →CVE-2026-97689 →CVE-2026-114406 →CVE-2026-13595 →CVE-2026-27456 →CVE-2026-53613 →

📋 Description

CVE-2026-13595 — util-linux: util-linux: heap use-after-free in libblkid nested partition probing CVE-2026-27456 — util-linux: TOCTOU in the mount program when setting up loop devices CVE-2026-53612 — util-linux: util-linux: TOCTOU in the mount program when applying post-mount ownership/mode changes CVE-2026-53613 — util-linux: TOCTOU in the mount program via ancestor directory swap on target path CVE-2026-53614 — util-linux: util-linux: SUID mount(8) allows nosuid/noexec bypass via LIBMOUNT_FORCE_MOUNT2 CVE-2026-53615 — util-linux: util-linux: Partition metadata compromise via integer overflow in DOS partition parser CVE-2026-76642 — util-linux: util-linux: failed external mount helper still runs privileged X-mount post-hooks CVE-2026-77214 — expat: expat: Information disclosure via heap buffer over-read in XML_ParseBuffer CVE-2026-78408 — util-linux: util-linux: nsenter --join-cgroup leaks root cgroup migration authority CVE-2026-78410 — util-linux: util-linux: restricted bind mounts do not pin the source, allowing X-mount.owner/group/mode redirection CVE-2026-97687 — urllib3: urllib3: Traffic interception via HTTPS proxy TLS configuration override CVE-2026-97689 — urllib3: urllib3: Denial of Service via unbounded memory allocation in chunk parser CVE-2026-102633 — expat: expat: Denial of Service via integer overflow in expat_realloc CVE-2026-114406 — ca-certificates: Distrust eMudhra intermediate CA certificates due to security concerns

🎯 Affected products2

  • Red Hat Cost Management On-Premise 1
  • registry.redhat.io/costmanagement/costmanagement-ui-rhel10@sha256:eccf74ca7737d3a53b5f4f5ad8cc786b592d97ab8c6ba02ce233bf09640b3b39_amd64 as a component of Red Hat Cost Management On-Premise 1

✅ Remediation

The container image provided by this update can be downloaded from the Red Hat container registry at registry.redhat.io using the "podman pull" command. 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 this flaw, remove the 'user' option from any loop mounts in the /etc/fstab file or ensure the the source path points to a root-owned directory where unprivileged users do not have write permissions. Workaround: In SUID/restricted mode, reject X-mount.mode= values containing SUID/SGID bits (04000/02000). Verify mount target path ancestor chain integrity before post-hook execution. Workaround: Review /etc/fstab and remove the user or users mount option from any entry where unprivileged user mounting is not strictly required. This eliminates the prerequisite for exploitation. For entries that must retain user mount capability, ensure all ancestor directories in the mount target path are owned by root and not writable by unprivileged users (mode 0755 or stricter), preventing the renameat2(RENAME_EXCHANGE) directory swap needed to exploit the race. These changes take effect immediately with no reboot required. Workaround: In the legacy bind path, use mount_setattr() to apply security flags atomically, eliminating the window between the two syscalls. Add SUID regression test: LIBMOUNT_FORCE_MOUNT2=always must not change API path selection for unprivileged callers. Workaround: Red Hat is not aware of a practical temporary workaround that fully mitigates this issue or meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the relevant security updates when/if they become available. Workaround: Avoid combining the user (or users) fstab option with X-mount.idmap or X-mount.owner/group/mode on entries that invoke an external mount.<type> helper. Administrators can also remove or restrict user-mountable fstab entries that specify those X-mount.* options. Workaround: Upgrade to util-linux v2.41.6, v2.42.3, or later. Until a fix is applied, do not run nsenter --join-cgroup (including nsenter --target PID --all --join-cgroup) against untrusted processes or namespaces. The fix closes the cgroup.procs descriptor immediately after joining, and opens it with O_CLOEXEC. Workaround: Upgrade to util-linux v2.41.6, v2.42.3, or later. Until a fix is applied, do not allow unprivileged /etc/fstab bind or rbind entries that also specify X-mount.owner, X-mount.group, or X-mount.mode, especially when the bind source is below a user-writable ancestor. 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: See the security bulletin for a detailed mitigation procedure.

🔗 References (20)