RHSA-2026:88199HighCVSS 7.5

Red Hat Security Advisory: LVMS 4.12 Bug Fix and Enhancement update

Published
October 22, 2026
Last Modified
November 3, 2026

🔗 CVE IDs covered (8)

CVE-2026-56859 →CVE-2026-56860 →CVE-2026-56862 →CVE-2025-68121 →CVE-2026-32280 →CVE-2026-33811 →CVE-2026-33818 →CVE-2026-42504 →

📋 Description

CVE-2025-68121 — crypto/tls: crypto/tls: Incorrect certificate validation during TLS session resumption CVE-2026-32280 — crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building CVE-2026-33811 — net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME CVE-2026-33818 — encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal CVE-2026-42504 — mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header CVE-2026-56859 — encoding/xml: golang: Go: Denial of Service via XML decoding recursion depth issue CVE-2026-56860 — net/url: golang: golang net/url: Denial of Service from quadratic complexity in path resolution CVE-2026-56862 — crypto/tls: golang: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages

🎯 Affected products14

  • Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/lvms-must-gather-rhel8@sha256:46bfe8b830548a0f8c2bd5908f569dabd9bf0b2df0f444ac90c9f196b08e7526_arm64 as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/lvms-must-gather-rhel8@sha256:944c9e33b240ab584ffc67bf0421ab56defa359ca2261b5b4e8ec45b134c859e_s390x as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/lvms-must-gather-rhel8@sha256:aeedd116f439373b0ffd779d383a8139e3aa6c2465a81a99d31ed485f93c7136_ppc64le as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/lvms-must-gather-rhel8@sha256:b8fca1683e03e5c2f3a981f8f3b7e41fcbd5376d81a24819f9af9a654cbfe0d8_amd64 as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/lvms-operator-bundle@sha256:62efb19ba31393591b35485e779aa0d28b5e038d5007159bf2a5f92f0ec813d5_amd64 as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/lvms-rhel8-operator@sha256:0e5b2b2c9e36eb7604976e556aad35245a3254e60e5f258fde028ba8c17ef643_amd64 as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/lvms-rhel8-operator@sha256:2089cc8e6c235795da7a00f7e97a9728457b990148bae4f50814b856cf16e52d_s390x as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/lvms-rhel8-operator@sha256:561e7ea7f530d6a07f70844dd7f88cfe22a3007879b607204fa1402257769e96_ppc64le as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/lvms-rhel8-operator@sha256:ff47e0294472c280c372ffb6b264bb8dac2a79354b9a55f704a9eca145722e94_arm64 as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/topolvm-rhel8@sha256:57dcfc35580789fffea3095951537def03dc36d6bd99bb7f59c459920cb46a3c_amd64 as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/topolvm-rhel8@sha256:58201e92b1db47183d2f8c41c08dbe256d4180cb64d84a63a0637ea556fc2a99_ppc64le as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/topolvm-rhel8@sha256:5f0847d9942e1091f48cab27db5f6350e07c0645b9b154141d98aac630d51f0b_s390x as a component of Logical Volume Manager Storage 4.12
  • registry.redhat.io/lvms4/topolvm-rhel8@sha256:639f7535378635b9116ff6fa387ff07c20caa72d32173fd22b3cbcc8d670b353_arm64 as a component of Logical Volume Manager Storage 4.12

✅ 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://access.redhat.com/articles/11258 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 issue, applications can be configured to use the pure Go DNS resolver instead of the `cgo` DNS resolver. This can be achieved by setting the `GODEBUG` environment variable to `netdns=go`. For example, to run a Go application with this mitigation: `GODEBUG=netdns=go /path/to/your/go/application`. This change may require restarting affected applications or services to take effect. Users should verify that this change does not negatively impact DNS resolution for their specific application environment. Workaround: To mitigate this issue, restrict network access to services that process MIME headers from untrusted sources. Implement input validation and sanitization for all incoming data, especially MIME headers, to prevent maliciously crafted content from being processed by applications utilizing the vulnerable Golang MIME package.

🔗 References (11)