CVE-2026-94651 is a high-severity vulnerability in Apache Thrift's Java bindings affecting versions before 0.25.0. It involves improper handling of exceptional conditions leading to missing release of resources after their effective lifetime. This flaw is fixed in version 0.25.0, and users are advised to upgrade to this version to mitigate the issue.
CVE-2026-93926 is a high-severity vulnerability in Apache Thrift before version 0.25.0 involving missing release of memory and resources after their effective lifetime in the THeaderTransport component. This can lead to resource exhaustion or memory leaks. The issue is fixed in Apache Thrift version 0.25.0.
CVE-2026-102723 is a high-severity vulnerability in Eclipse ThreadX NetX Duo versions 6.4.0 through 6.5.2.202603a when built with VLAN and SRP support. It involves a NULL pointer dereference caused by the MSRP attribute lookup writing through a null pointer when the attribute table is full. An unauthenticated attacker on the same Layer 2 segment can trigger this fault by declaring enough new attributes, leading to a fault in the MRP worker thread. Talker Failed declarations exacerbate the issue by holding table entries indefinitely.
CVE-2026-97686 is a medium severity vulnerability in Wind River VxWorks 7 prior to version 26.09. It involves the IPNET subsystem failing to release allocated kernel memory and system file descriptors when certain system call arguments are used, leading to resource leaks. This issue is fixed in version 26.09.
CVE-2026-79677 is a high-severity vulnerability in Apache Tomcat involving a missing release of resources after their effective lifetime, specifically related to asynchronous WebSocket writes. This flaw can cause denial of service due to lost timeouts. It affects multiple versions across several major Tomcat branches, including 7.0.43 through 7.0.109, 8.5.0 through 8.5.100, 9.0.0.M1 through 9.0.121, 10.1.0-M1 through 10.1.59, and 11.0.0-M1 through 11.0.25. Fixed versions are 11.0.26, 10.1.60, and 9.0.122.
CVE-2026-92230 is a high-severity vulnerability in Apache Karaf where static ThreadLocal fields cache XML parser/transformer factories on long-lived container threads. This causes memory from successive bundle ClassLoaders to be retained and unreachable for garbage collection after bundle lifecycle operations, leading to unbounded Metaspace growth and potential denial of service.
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. From 3.0.8 until 3.0.12, a client with maxConnections or maxConnectionsPerHost set above zero leaks one connection permit whenever TLS connection establishment fails before the handshake completes. NettyConnectListener removes the partitionKeyLock permit from NettyResponseFuture before every failure path is bound to the channel closeFuture, so an abort can leave the permit unreleased. Repeated failures can permanently lock out one host under a per-host limit or drain the shared pool under a global limit, blocking later requests even when no connection remains open. The default unlimited connection setting is not affected. This issue is fixed in version 3.0.12.
RMCP is an official Rust SDK for the Model Context Protocol. Prior to 2.0.0, the rmcp crate's stateful Streamable HTTP server in crates/rmcp/src/transport/streamable_http_server/tower.rs allows an unauthenticated client to send a well-formed JSON-RPC POST that is not an initialization request, or an initialization request with a mismatched protocol header, causing StreamableHttpService::handle_post to call LocalSessionManager.create_session before validating the message. An early validation failure returns without removing the inserted LocalSessionHandle from LocalSessionManager.sessions, permanently retaining session and channel state for the server process lifetime. Repeated requests can grow the shared session table without bound, degrade legitimate-client latency through lock contention, exhaust memory, and terminate the server. This issue is fixed in version 2.0.0.
CVE-2026-72931 is a vulnerability in Microsoft Windows 10 Version 1607 related to the Secure Socket Tunneling Protocol (SSTP). It involves a missing release of a resource after its effective lifetime, which can be exploited by an authorized local attacker to cause a denial of service. The issue affects multiple Windows 10 builds and earlier Windows versions. Microsoft has issued official fixes for all affected versions.
CVE-2026-69664 is a denial of service vulnerability in the Erlang/OTP inets httpd component. An unauthenticated remote attacker can send a specially crafted HTTP request with a chunked body containing a non-hexadecimal chunk-size line. This causes the worker handling the connection to become stuck and never released, exhausting all available workers and denying service to legitimate clients. The default configuration is affected, and no authentication is required to exploit this issue.
CVE-2026-71380 is a denial of service vulnerability in Erlang/OTP's inets httpd component. An unauthenticated remote attacker can send a valid HTTP request with a large Content-Length header and then stall before sending the full body, causing server workers to wait indefinitely. This exhausts available workers and denies service to legitimate clients at minimal bandwidth cost. The issue affects OTP versions from 17.0 up to but not including 27.3.4.17 and corresponding inets versions from 5.10 up to but not including 9.3.2.7. Fixed versions are OTP 27.3.4.17 and inets 9.3.2.7.
CVE-2026-59320 is a resource management vulnerability in Spring AMQP version 4.1.0. When a container-level ErrorHandler is configured, each message delivery that throws an exception permanently consumes one link credit. After 100 such failing messages (the default initialCredits), the receiver's credit is exhausted, causing the message broker to stop delivering messages and leaving the listener stalled while still appearing to run.
CVE-2026-77384 is a high-severity vulnerability in the JavaScript implementation of libp2p (js-libp2p) prior to version 4.2.9. It involves uncontrolled resource consumption due to repeated registration of abort listeners on every reservation refresh in the reservation-store.ts component. This flaw allows a remote peer to send repeated valid RESERVE requests, causing unbounded growth of listeners and closures in @libp2p/circuit-relay-v2 relay servers, leading to denial of service. The issue is fixed in version 4.2.9.
CVE-2026-59654 is a resource management vulnerability in Apache CloudStack affecting scoped global configuration functionality across various modules and plugins. It impacts versions from 4.7.0 through 4.20.3.0 and 4.21.0.0 through 4.22.1.0. The flaw may cause a denial of service (DoS) condition on the management server due to missing release of resources after their effective lifetime. Fixed versions are 4.20.3.1 and 4.22.1.1 or later.
In Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series), sensitive key material held by the AES and DESede engines, the SP 800-90A DRBGs, SymmetricSecretKey and the PBKD and scrypt parameter classes was zeroised on garbage collection by overriding Object.finalize. Finalization runs at an unspecified time and in an unspecified order and is serviced by a single finalizer thread, so where objects carrying a finalizer are allocated faster than that thread retires them the pending-finalization queue grows without bound: disposal falls arbitrarily far behind, which can contribute to an OutOfMemoryError under load, and the key material those objects hold stays resident in the heap for as long as they are queued, defeating the purpose of the zeroisation. The behaviour was not a problem on Java 8 or Java 11; it is later JVMs, on which finalization has been deprecated and progressively de-emphasised, where it becomes one. Disposal of these classes now runs from a java.lang.ref.Cleaner registered in the multi-release jdk1.9 overlay, so on Java 9 and later it no longer depends on the finalizer being scheduled. Bouncy Castle for Java (bcprov) and Bouncy Castle for Java LTS are not affected, as neither implements the finalizer-based zeroisation scheme.
Klever-Go is the Go implementation of the Klever blockchain protocol. In versions prior to 1.7.18, the account-data trie syncers are vulnerable to a resource-exhaustion flaw that leaks bounded throttler slots on error paths. In syncDataTrie() (in both userAccountsSyncer.go and kappAccountsSyncer.go), StartProcessing() reserves a slot from the NumGoRoutinesThrottler, but the corresponding EndProcessing() is only called on the success path and on the duplicate-root early return. As a result, any error from trie.NewTrie(), trie.NewTrieSyncer(), or trieSyncer.StartSyncing() (including the network-dependent timeout path) permanently consumes one slot for the lifetime of the throttler. An attacker who can repeatedly cause trie-node sync failures or timeouts during bootstrap can exhaust the bounded throttler, after which further account-data trie syncs stop making progress and SyncAccounts() returns a timeout. Because epoch bootstrap in syncUserAccountsState() and syncKappAccountsState() aborts on any such error, this causes bootstrap to fail, a core availability issue affecting fresh, restarting, or resyncing nodes and validators. This issue is fixed in version 1.7.18.
Eclipse Milo versions 1.0.0 through 1.1.4 contain a vulnerability where monitored-item quota accounting is not exception-safe. An unauthenticated remote client can trigger a StackOverflowError by sending deeply nested PubSub ExtensionObjects in a CreateMonitoredItems event filter. This causes the server-global monitored-item quota to be exhausted and prevents new monitored items from being created until the server is restarted. Existing monitored items and other server functions remain unaffected.