Red Hat OpenShift Container Platform 4.21.35 includes security updates addressing multiple vulnerabilities in Go language components. These vulnerabilities involve denial of service via malformed HTTP/2 frames, excessive recursion in ASN.1 unmarshalling, malicious MIME headers, XML decoding recursion depth issues, quadratic complexity in URL path resolution, indefinite TLS KeyUpdate messages, and cross-site scripting via pathological input. Users of OpenShift Container Platform 4.21 are advised to upgrade to the updated packages and images to mitigate these issues.
This advisory concerns OpenShift Virtualization v4.21 images from Red Hat, which address several bugs and enhancements. The advisory references CVE-2026-56862, classified as a high severity vulnerability related to CWE-1050. No known exploits are reported in the wild. The update includes new images for Red Hat Container Native Virtualization. The vendor recommends applying this update after ensuring all previous errata are applied.
Red Hat OpenShift Container Platform 4.21.35 includes a security update addressing multiple vulnerabilities. This update fixes several bugs and adds enhancements to the container images and RPM packages. Users of OpenShift Container Platform 4.21 are advised to upgrade to this release to apply the security fixes.
CVE-2026-96745 is a medium severity vulnerability in the MongoDB PHP Driver involving deserialization of untrusted data in the command monitoring feature. An unauthenticated attacker who controls data included in a database operation can cause the driver to instantiate application classes implementing the driver's persistable interface, invoking their unserialization methods with attacker-supplied data. The impact depends on the classes present in the application. This vulnerability affects multiple version ranges of the MongoDB PHP Driver prior to fixed versions 1.21.10, 2.1.10, and 2.5.3.
CVE-2026-41178 is a denial of service vulnerability in OpenTelemetry-Go affecting Red Hat products that use this component. The flaw allows a remote attacker to cause resource exhaustion by sending oversized or invalid baggage headers, which the vulnerable Parse function fails to properly reject. This leads to excessive processing and error logging, potentially disrupting service availability. The vulnerability affects Red Hat Trusted Artifact Signer (RHTAS) used with OpenShift Container Platform versions 4.16 through 4.21. No fix is currently available as per the vendor advisory.
A vulnerability was determined in Saleor up to 3.20.118/3.21.54/3.22.47/3.23.14. This vulnerability affects the function get_client_ip of the file saleor/account/throttling.py. Executing a manipulation can lead to improper restriction of excessive authentication attempts. The attack can be executed remotely. The attack requires a high level of complexity. It is stated that the exploitability is difficult. The exploit has been publicly disclosed and may be utilized. The projects own issue #19203 internal ticket admits "IP can be spoofed in most deployments" and that its REAL_IP_ENVIRON-type setting bypasses get_client_ip; fix (right-to-left RFC 7239 hop selection) proposed but still unmerged. The vendor explains within an email, that "[t]his is not a vulnerability, this is working at intended, Saleor expects XFF to be configured properly".
CVE-2026-75029 is a medium severity vulnerability in ISC BIND 9 that allows an attacker to cause asymmetric resource consumption via amplification. By sending multiple copies of a record that should only exist once in a query response, such as an SOA record with identical RDATA, the BIND server appends these to the in-memory RDATA set. This behavior increases memory usage of the negative cache and may lead to other memory-related attack vectors. The vulnerability affects multiple BIND 9 versions from 9.11.0 through 9.21.25 and their respective S1 variants.
On a resolver configured to use ``dns64``, if an applicable answer from the authoritative server is malformed in a specific way, the resolver `named` process will exit unexpectedly. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
For a secondary zone with transfers restricted by TSIG, `named` may start to serve the data provided in a zone transfer before the final message with the TSIG signature arrives. This could allow an attacker that does not actually possess a valid TSIG signature to send unauthorized zone contents to a secondary server. Although no TSIG signature ever arrives, `named` does not rollback to the pre-transfer state. To exploit the vulnerability, the transfer must be a multi-message TCP IXFR, as described by RFC 8945. This issue affects BIND 9 versions 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, 9.11.3-S1 through 9.18.50-S1, and 9.20.9-S1 through 9.20.27-S1.
CVE-2026-81736 is a high-severity vulnerability in ISC BIND 9 that causes excessive CPU consumption when a resolver with cached SVCB/HTTPS AliasMode records is queried for the root of that tree. This affects multiple BIND 9 versions including 9.18.x, 9.20.x, 9.21.x, and their respective S1 variants. The issue results in disproportionate CPU usage during response construction, potentially leading to denial of service conditions.
CVE-2026-19667 is a numeric truncation error vulnerability in ISC BIND 9's named DNS service. An attacker-controlled authoritative DNS server can send a crafted negative response of exactly 65536 bytes, causing named to create a zero-byte negative cache entry. Subsequent accesses to this cache entry cause the named service to abort, resulting in a denial of service. This affects multiple BIND 9 versions including 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and their S1 variants.
CVE-2026-19941 is a vulnerability in ISC BIND 9 where an inapplicable NSEC record may be accepted by a named resolver as proof that no wildcard DNS record exists. This can allow an attacker at the same or upstream zone level to mask the existence of a victim's wildcard record. The issue affects multiple versions of BIND 9, including 9.11.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and their respective S1 variants. The CVSS score is 5.9, indicating a medium severity impact with no confidentiality loss but potential integrity impact.
CVE-2026-81563 is a high-severity memory management vulnerability in ISC BIND 9. It occurs when a BIND resolver processes an SVCB/HTTPS AliasMode record referencing 14 or more SVCB/HTTPS ServiceMode records, leading to failure in releasing internal resources. This can cause resource exhaustion and prevent new recursive DNS lookups. The vulnerability affects multiple BIND 9 versions from 9.18.0 through 9.18.50, 9.20.0 through 9.20.27, 9.21.0 through 9.21.25, and several S1 variants. No patch or remediation details are provided, and no known exploits are reported in the wild.
A vulnerability exists in the Oracle Net Services component of Oracle Database Server versions 21.3 through 21.23 and 23.4.0 through 23.26.3. This flaw allows an unauthenticated attacker with network access to cause a denial of service by hanging or crashing Oracle Net Services. The vulnerability has a CVSS 3.1 base score of 7.5, indicating high severity with impact on availability only. Oracle has released security patches addressing this and many other vulnerabilities in their September 2026 Critical Security Patch Update advisory.