basic-ftp versions prior to 6.2.3 contain an uncaught exception vulnerability in FTPContext.send() when commands include carriage return, line feed, or NUL characters. This flaw can cause the Node.js process to terminate unexpectedly during certain FTP operations, such as login or resumed downloads, due to exceptions escaping normal promise error handling. The issue is fixed in version 6.2.3.
CVE-2026-123805 is an out-of-bounds read vulnerability in the sipsorcery library prior to version 10.0.14. The flaw occurs in the SCTP SACK chunk parser, where attacker-controlled fields are read without proper bounds checking, leading to an IndexOutOfRangeException. This exception causes the SCTP association and all related data channels to terminate permanently. The issue is fixed in version 10.0.14.
CVE-2026-120222 is a vulnerability in the undici HTTP client for Node.js affecting versions 7.0.0 through 7.30.1 and 8.0.0 through 8.12.3. When the cache interceptor is used with a downstream response handler that throws during processing, an asynchronous throw can escape as an uncaught exception or unhandled promise rejection, causing the Node.js process to terminate. This can be triggered by a malicious or compromised HTTP server serving a cacheable response that causes the throw on replay, impacting availability. The issue is fixed in versions 7.30.2 and 8.12.4. Users are advised to upgrade to these fixed versions or later or avoid composing the cache interceptor with such response handlers until upgrading.
CVE-2026-100300 is a high-severity vulnerability in Apache ZooKeeper affecting versions 3.8.0 through 3.8.7 and 3.9.0 through 3.9.6. It involves improper handling of exceptional conditions in the quota subsystem, allowing an attacker with write access under the /zookeeper/quota subtree to crash the server's critical request-processing thread. On default deployments where this subtree is world-writable and unauthenticated, this can lead to permanent unbootability of the on-disk data directory. Upgrading to Apache ZooKeeper versions 3.8.8 or 3.9.7 resolves the issue.
HCL BigFix AEX version 13.0.0.1 contains an information disclosure vulnerability due to improper error handling. This flaw allows error messages to reveal sensitive technical details such as stack traces, system information, or internal paths. Such disclosures could aid attackers in crafting further attacks against the system.
When parsing an AS range in Routinator, if the maximum value of the range is smaller than the minimum value of the range, Routinator will never reach the maximum value and run out of memory.
Routinator runs out of open connections on the HTTP server when many connections are opened but never closed, leaving the HTTP server unavailable. This condition can be triggered maliciously by an attacker by opening a large number of connections to the HTTP server.
This only affects users that make their HTTP or RTR server available to untrusted networks.
Routinator exits when an rsync URI for a file obtained over RRDP contains a path that cannot be stored on disk, such as too long file names, and folder names that overlap with existing file names.
Routinator stores a newly-retrieved TA certificate via HTTPS in cache without validation, potentially overwriting a known good TA certificate even if validation fails.
When Routinator encounters a CRL with many entries, it may hang or run out of memory. If Routinator encounters a CRL file with the wrong encoding, it may exit.
When Routinator encounters an RRDP notification file with gaps in the delta entries, it is still accepted and parsed, potentially leading to missing data. If it encounters too many delta entries it may run out of memory.
Routinator runs out of memory when the JSON output is requested many times concurrently. This condition can be triggered maliciously by an attacker by opening a large number of connections to the HTTP server. Additionally Routinator runs into a stack overflow and exits when a payload item with too much metadata is discarded at once.
This only affects users that make their HTTP or RTR server available to untrusted networks.
PHP has various global state that temporarily points into request memory. In some scenarios, global state may not be correctly reset, or may be repopulated after being reset. The global state may then refer to request memory even after it has been freed. Subsequent requests may read or branch on this stale state before it is fully initialized. Multiple strategies can trigger this condition and produce remote code execution (RCE).
PHP uses longjmp() for out-of-memory (OOM) errors to exit the current context and abort handling of the request. Some contexts may not properly account for this scenario and leave request memory in an uninitialized state before performing an allocation. The subsequent request cleanup procedure may read or branch on this memory. Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).
CVE-2026-103936 is a high-severity vulnerability in the JavaScript libp2p networking stack prior to version 6.0.28. The issue arises in the @libp2p/webrtc webRTCDirect() Node.js listener, which processes unauthenticated STUN Binding Requests before completing peer authentication and connection setup. A crafted short ICE password derived from the STUN request causes an uncaught native invalid_argument exception in node-datachannel or libdatachannel, leading to process termination (SIGABRT). This denial of service vulnerability does not affect confidentiality, integrity, or allow code execution. The issue is fixed in libp2p version 6.0.28.
A protection mechanism failure exists in Coraza WAF versions 3.4.0 through 3.7.x in the multipart processor. The processor treats io.ErrUnexpectedEOF as nonfatal without setting the MULTIPART_STRICT_ERROR flag, allowing truncated multipart bodies to bypass certain defensive rules. This can lead to multipart parser-disagreement payloads reaching backend systems that interpret the truncated body differently. The issue is fixed in version 3.8.0.
CVE-2026-105242 is a medium severity vulnerability in Apache log4net affecting versions from 1.2.11 up to but not including 3.5.0. It involves improper handling of exceptional conditions in the aspnet-request pattern converter. When request parameters trigger ASP.NET request validation and contain markup, the layout throws an exception causing the appender to discard the entire log event. This allows a sender to suppress logging of their own request. The issue only affects applications running on ASP.NET for .NET Framework that use the %aspnet-request layout pattern. Upgrading to version 3.5.0 resolves the vulnerability.
vLLM is an inference and serving engine for large language models. Prior to 0.30.0, structured-output request failures can escape request-scoped validation and reach the EngineCore fatal-error path. A per-request backend mismatch can re-raise a grammar compilation exception, padding produced by the ngram_gpu speculative-decoding mode can pass a negative token to guidance validation, and the Rust frontend can admit empty structured-output values that the Python frontend rejects, allowing ordinary constrained-generation requests to terminate the shared engine. This issue is fixed in version 0.30.0.