RHSA-2026:95264CriticalCVSS 8.2

Red Hat Security Advisory: Cost Management Metrics Operator Update

Published
November 4, 2026
Last Modified
November 10, 2026

🔗 CVE IDs covered (13)

CVE-2026-89157 →CVE-2026-89158 →CVE-2026-89161 →CVE-2026-103111 →CVE-2026-77117 →CVE-2026-80489 →CVE-2026-84782 →CVE-2026-86145 →CVE-2026-114406 →CVE-2026-6368 →CVE-2026-6791 →CVE-2026-18374 →CVE-2026-19542 →

📋 Description

CVE-2026-6368 — glibc: glibc: Process abort due to invalid memory in wordexp CVE-2026-6791 — glibc: Glibc: Denial of Service via stack exhaustion during tilde expansion CVE-2026-18374 — glibc: glibc: Heap buffer overflow via attacker-controlled fopen mode string CVE-2026-19542 — glibc: Fix out-of-bounds array write in tdelete CVE-2026-77117 — glibc: Non-progress DoS in SHIFT_JISX0213 -&gt CVE-2026-80489 — glibc: Non-progress DoS in EUC_JISX0213 -> UCS-4 conversion state CVE-2026-84782 — openssl: compat-openssl: openssl: Information disclosure via DTLS handshake retransmission CVE-2026-86145 — pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions CVE-2026-89157 — pcre2: PCRE2: Out-of-bounds write via large pattern input CVE-2026-89158 — PCRE2: PCRE2: Out-of-bounds write via integer overflow on 32-bit platforms CVE-2026-89161 — pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match CVE-2026-103111 — pcre2: pcre2: Out-of-bounds write via crafted regular expression CVE-2026-114406 — ca-certificates: Distrust eMudhra intermediate CA certificates due to security concerns

🎯 Affected products6

  • Cost Management 4
  • registry.redhat.io/costmanagement/costmanagement-metrics-operator-bundle@sha256:86a97ab9093a9a2290d3e51ce671c5f62dfcdd86dea9862d1f6c03c310980ae3_amd64 as a component of Cost Management 4
  • registry.redhat.io/costmanagement/costmanagement-metrics-rhel9-operator@sha256:baeabe0fb1ffca46625c974966f6c5bd0f870e4a757b1afd421a123ece4e0b25_arm64 as a component of Cost Management 4
  • registry.redhat.io/costmanagement/costmanagement-metrics-rhel9-operator@sha256:c1b98ef61140fa706f3256859f98bf9621ad6b3bda8a5f1884e59b0be2b175d0_s390x as a component of Cost Management 4
  • registry.redhat.io/costmanagement/costmanagement-metrics-rhel9-operator@sha256:e1a40b10fc31b73dd4b5fdb274d109d740fe7dcbe2fddb2258e7e13f75ae865e_amd64 as a component of Cost Management 4
  • registry.redhat.io/costmanagement/costmanagement-metrics-rhel9-operator@sha256:fe9c5ec37b17a95787a67724231975f837bb8c259656cab45b3b6438c3b0efc6_ppc64le as a component of Cost Management 4

✅ Remediation

Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://docs.openshift.com/container-platform/latest/operators/admin/olm-upgrading-operators.html 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: This issue is reachable only through applications that use glibc's tsearch/tdelete APIs and allow construction of extremely deep trees (on the order of a million nodes). Restrict such services to trusted clients and enforce process memory limits so large tree growth is impractical. Workaround: Do not convert untrusted input using the SHIFT_JISX0213 character set (for example via iconv). Where conversion cannot be avoided, apply process CPU time limits and container cgroup resource limits so a hung converter cannot exhaust host resources. Workaround: To mitigate this avoid converting untrusted data with that charset, or disable the conversion path if unused. Where conversion of untrusted input cannot be avoided, restrict access to trusted clients and apply process CPU/resource limits to contain hang impact. Workaround: To mitigate this Improper Protection of Alternate Path vulnerability, ensure that secondary execution branches—such as the reuse of cached memory workspaces—enforce the exact same size and boundary checks as the primary memory allocation paths. Limit exposure by preventing untrusted user input from directly controlling PCRE2 regular expressions, and strictly avoid utilizing recursive matching patterns when operating under a low heap limit. Apply a defense-in-depth strategy by validating all inputs comprehensively. Workaround: See the security bulletin for a detailed mitigation procedure.

🔗 References (18)