This update for thrift fixes the following issues:
- CVE-2026-41602: TFramedTransport frame size headers can lead to a uint32 integer overflow (bsc#1263557).
- CVE-2026-41604: Swift input with an invalid field range can lead to an out-of-bounds read and application crash
(bsc#1263492).
- CVE-2026-41605: compact protocol messages with large integer values can lead to integer overflow (bsc#1263438).
- CVE-2026-41606: crafted nested messages in c_glib dispatch can lead to uncontrolled recursion and denial of service
(bsc#1263365).
- CVE-2026-41607: crafted message with improper length validation can lead to an out-of-bounds read and potential
information disclosure (bsc#1263321).
- CVE-2026-41608: Unbounded Zlib Decompression in Python THeaderTransport (bsc#1272609).
- CVE-2026-41636: uncontrolled recursion in Node.js bindings can lead to denial of service via stack exhaustion
(bsc#1263322).
- CVE-2026-43871: TCompactProtocol varint byte-count limit (bsc#1272648).
- CVE-2026-45112: Unbounded Read Leading to Denial of Service (bsc#1272647).
- CVE-2026-48144: c_glib TLS Client Missing Hostname Verification (bsc#1272645).
- CVE-2026-48145: C++ TSSLSocket matchName() RFC 6125 Wildcard Bypass (bsc#1272658).
- CVE-2026-48586: TZlibTransport Decompression Size Limit (bsc#1272657).
- CVE-2026-49158: Ruby THeaderTransport ZLIB Decompression Bomb (bsc#1272656).
- CVE-2026-55968: Node.js quadratic-time DoS in server receive transports (bsc#1272650).
- CVE-2026-55969: integer overflow in TProtocol:checkReadBytesAvailable() (bsc#1272649).
- CVE-2026-55970: C++ heap out-of-bounds read in THeaderTransport:readHeaderFormat() (bsc#1272655).
- CVE-2026-55971: C++ ZLIB heap buffer overflow (write) in THeaderTransport:untransform() (bsc#1272653).
- CVE-2026-58023: c_glib heap out-of-bounds read in transport leftover-bytes path (bsc#1272654).
- CVE-2026-58389: Rust binary protocol non-strict path missing string size limit (bsc#1272652).
- CVE-2026-58662: C++ THeaderTransport:readString() info-header length bounds bypass (bsc#1272651).
- CVE-2026-82458: allocation of resources without limits or throttling in several bindings (bsc#1284076).
- CVE-2026-82459: integer underflow leading to out-of-bounds write in C++ 32 bit THeaderTransport (bsc#1284077).
- CVE-2026-85086: improper certificate validation and initialization of resource with insecure default in Perl bindings
(bsc#1284078).
- CVE-2026-85483: use of uninitialized resource and return of wrong status code in c_glib bindings (bsc#1284102).
- CVE-2026-85493: uncontrolled recursion in Dart and Java ME bindings (bsc#1284101).
- CVE-2026-85494: improper handling of length parameter, uncaught exception, inefficient algorithm complexity, improper
memory allocation and improper initialization of resources in several bindings (bsc#1284079).
- CVE-2026-86537: uncaught exception, infinite loop and integer underflow in D language bindings (bsc#1284123).
- CVE-2026-91135: heap-based buffer overflow in C++ THeaderTransport (bsc#1284100).
- CVE-2026-91137: improper validation of specified quantity in input leading to allocation of resources without limits
or throttling in PHP bindings (bsc#1284080).
- CVE-2026-93925: stack-based buffer overflow in the C++ THeaderProtocol (bsc#1284093).
- CVE-2026-93926: missing release of memory after effective lifetime in THeaderTransport (bsc#1284092).
- CVE-2026-94633: improper handling of length parameters and memory allocation with excessive size value in Dart
bindings (bsc#1284091).
- CVE-2026-94634: allocation of resources without limits or throttling and initialization of resource with insecure
default in Python bindings (bsc#1284099).
- CVE-2026-94635: imṕroper handling of length parameter and allocation of resources without limits or throttling in Lua
bindings (bsc#1284090).
- CVE-2026-94639: improper handling of exceptional conditions, allocation of resources without limits or throttling and
uncaught exception in Java bindings (bsc#1284098).
- CVE-2026-94642: uncaught exception in PHP bindings (bsc#1284081).
- CVE-2026-94644: allocation of resources without limits or throttling in PHP bindings (bsc#1284097).
- CVE-2026-94645: improper validation of specified quantity in input leading to allocation of resources without limits
or throttling in nodejs bindings (bsc#1284096).
- CVE-2026-94650: uncontrolled recursion in c_glib bindings (bsc#1284082).
- CVE-2026-94651: improper handling of exceptional conditions and no release of resource after effective lifetime in
Java bindings (bsc#1284095).
- CVE-2026-94653: inefficient algorithm complexity in PHP bindings (bsc#1284122).
- CVE-2026-94654: infinite loop in Python bindings (bsc#1284121).
- CVE-2026-94655: allocation of resources without limits or throttling and inefficient algorithm complexity in Lua
bindings (bsc#1284120).
- CVE-2026-94656: alocation of resources without limits or throttling in Ruby bindings (bsc#1284119).
- CVE-2026-94657: alocation of resources without
A security update for Red Hat Hardened Images RPMs addresses multiple vulnerabilities including a notable flaw in Node.js (CVE-2026-123872) that allows an authenticated remote attacker to bypass client certificate authentication policies via TLS renegotiation. This issue affects configurations using TLS 1.2 with different security requirements per hostname and can lead to unauthorized access to restricted endpoints. The update includes new versions of nodejs26 and related packages. Mitigations include enforcing TLS 1.3 or terminating TLS at a proxy that does not forward TLS 1.2 renegotiation.
A security advisory from Red Hat addresses multiple vulnerabilities in Red Hat Hardened Images RPMs, including a notable flaw in Node.js (CVE-2026-123872). This Node.js vulnerability allows an authenticated remote attacker to bypass client certificate authentication policies by renegotiating TLS 1.2 connections and changing the target server name, potentially gaining unauthorized access to restricted endpoints. The issue affects deployments where Node.js directly handles TLS termination with heterogeneous mutual TLS policies using TLS 1.2. Enforcing TLS 1.3 or terminating TLS at a proxy that does not forward TLS 1.2 renegotiation mitigates the risk. The advisory includes updates to various nodejs24 RPM packages to address these issues.
A security advisory from Red Hat addresses multiple vulnerabilities in Red Hat Hardened Images RPMs, including a significant flaw in Node.js (CVE-2026-123872). This Node.js vulnerability allows an authenticated remote attacker to bypass client certificate authentication policies by exploiting TLS renegotiation in TLS 1.2, potentially gaining unauthorized access to restricted endpoints. The issue affects deployments where Node.js directly handles TLS termination with multi-tenant domains using different mutual TLS policies. Mitigations include enforcing TLS 1.3 or terminating TLS at a proxy that does not forward TLS 1.2 renegotiation. The advisory provides updated RPM packages to address these issues.
A vulnerability in Node.js allows a client authorized for the default hostname to bypass per-host mutual TLS (mTLS) authorization and access a protected hostname it is not authorized for. This occurs when a TLS server configures a hostname with a client-certificate CA but no server certificate, causing the client CA to fall back to the default. As a result, a client trusted by the default CA can complete mTLS to the protected hostname despite lacking proper authorization. This affects Node.js versions 22.x, 24.x, and 26.x.
A use-after-free vulnerability exists in Node.js HTTP/2 when serving files using respondWithFile() or respondWithFD(). An unauthenticated client can cause the server to free an Http2Stream object while a write operation referencing it is still queued, leading to a dereference of freed memory. This affects Node.js versions 26.x starting from 26.9.0 and 24.x starting from 24.22.0. The vulnerability can be triggered over both TLS and cleartext connections.
A NULL pointer dereference vulnerability in Node.js HTTP/2 allows an unauthenticated client to crash the server by cancelling file downloads. This affects Node.js versions 22.x, 24.x, and 26.x. The issue occurs when the server uses stream.respondWithFile() or stream.respondWithFD() to serve files, and the client cancels the request, causing a StreamPipe to be torn down improperly and leading to a NULL pointer dereference that aborts the process. No special crafted frames are required to trigger the crash.
A vulnerability in Node.js TLS allows a client to bypass client certificate authentication by changing the servername during TLS 1.2 renegotiation. This enables a client authenticated for a less restrictive host to access endpoints with stricter client-certificate policies, effectively bypassing intended access controls. The issue affects Node.js versions 22.x, 24.x, and 26.x.
A use-after-destroy vulnerability exists in Node.js TLS server handshake handling when using certain OpenSSL callbacks. This flaw allows a remote, unauthenticated attacker to cause the Node.js server process to terminate unexpectedly by sending a specially crafted client hello message followed by a socket FIN. The issue affects Node.js versions 24.x and 26.x and results in an uncaught exception that crashes the server process.
A re-entrancy vulnerability in Node.js HTTPS allows an unauthenticated client to read memory from other connections, potentially exposing TLS private keys and other users' request data. This occurs due to a use-after-free and out-of-bounds heap read triggered by specific sequences of HTTP response handling involving res.flushHeaders() and res.end(). The flaw affects Node.js versions 22.x, 24.x, and 26.x.
An unauthenticated HTTP/2 client can cause a Node.js server to leak memory and file descriptors indefinitely by triggering a protocol error during session shutdown. This leaves sockets in CLOSE_WAIT state and HTTP/2 session state held in memory without release. The issue affects Node.js versions 22.x, 24.x, and 26.x and is a partial regression of a previous fix (CVE-2026-48937).
CVE-2026-123868 is a vulnerability in Node.js versions 24.x and 26.x where an unauthenticated HTTP/2 client can exhaust server memory. The issue arises because inbound DATA frames queued on an undrained stream are not properly accounted against the session memory budget, allowing excessive memory retention. This can lead to denial of service by exhausting server resources.
A reachable assertion vulnerability in Node.js HTTP/2 session teardown allows any unauthenticated client to abort the server process. This occurs because an Http2Stream holding nghttp2-allocated header buffers can outlive its session, causing a failed assertion during session destruction. The issue affects Node.js versions 26.x (since 26.9.0) and 24.x (since 24.22.0) and is a variant of a previously fixed vulnerability (CVE-2024-27983).
Node.js versions 22.x, 24.x, and 26.x disclose proxy credentials in ERR_PROXY_INVALID_CONFIG error messages. This occurs because certain error paths interpolate the raw proxy URL, including sensitive credentials, into error messages that are exposed to stderr, logs, and crash reporting services. The vulnerability results from incomplete redaction of proxy credentials in error outputs.
A vulnerability in the Node.js zlib streaming API allows an uncatchable exception to crash a process when a peer disconnects during compression. This occurs because zlib.params() queues a flush operation that completes in a callback, which asserts on a native handle that may no longer exist if the stream is destroyed, causing an internal assertion error that terminates the process. The issue affects Node.js versions 22.x, 24.x, and 26.x and requires the application to call deflate.params() while streaming to a peer, which is uncommon.
CVE-2026-123866 is a use-after-free vulnerability in Node.js HTTP/2 stream teardown that can leak response memory, including data from other connections' response buffers, to a peer. This occurs when a stream is torn down while a write is still backpressured, causing freed or unrelated heap memory to be sent instead of the intended response. The flaw affects Node.js versions 22.x, 24.x, and 26.x. The vulnerability has a high severity score of 7.5 and impacts confidentiality but not integrity or availability.
A certificate validation bypass vulnerability exists in Node.js https.Agent where cached TLS sessions authenticated under a broader CA policy can be reused in connections with stricter CA policies. This occurs because the session cache key does not differentiate between omitted and empty CA arrays, allowing a TLS 1.3 session authenticated with the default trust store to be resumed in a connection that explicitly supplies an empty CA list. This leads to unauthorized acceptance of TLS sessions and potential exposure of confidential data. The issue affects Node.js versions 22.x, 24.x, and 26.x.
The teahy-znrpz-util npm package contains malicious code that executes hidden payloads on module load. It stores obfuscated executable logic as a compressed byte array in a non-standard package.json key, decompresses it, and runs it with full Node.js privileges. The code avoids execution in CI or sandbox environments, targeting real developer or production machines.