vLLM is an inference and serving engine for large language models. Prior to 0.30.0, OpenAI-compatible request models accept a non-empty cache_salt value without enforcing the character and length restrictions required by the IPCCacheServerKey consumer in LMCache-MP. On deployments using the LMCache-MP connector, a salt that contains a forbidden character or exceeds the permitted length can raise an uncaught ValueError during scheduler cache lookup, causing EngineCore to terminate and denying service to all concurrent users. This issue is fixed in version 0.30.0.
Apache Thrift versions before 0.25.0 contain an uncaught exception vulnerability in the Perl bindings. This flaw can lead to high-severity impacts if exploited. The issue is resolved in version 0.25.0, which users are advised to upgrade to.
CVE-2026-94646 is a high-severity vulnerability in Apache Thrift's Node.js bindings affecting versions before 0.25.0. It involves uncaught exceptions, improper validation of input quantities, and prototype pollution due to improperly controlled modification of object prototype attributes. This vulnerability can lead to significant security risks if exploited. Users are advised to upgrade to version 0.25.0, which addresses and fixes the issue.
CVE-2026-90440 is a high-severity vulnerability in Apache Thrift prior to version 0.25.0. It involves uncaught exceptions and improper handling of exceptional conditions in the thrift.server.nonblocking.TNonblockingServer component, leading to improper resource shutdown. This can cause service disruption or other impacts related to resource management. Users are advised to upgrade to Apache Thrift version 0.25.0, which addresses this issue.
CVE-2026-86537 is a high-severity vulnerability in Apache Thrift's D language bindings affecting versions before 0.25.0. It involves an uncaught exception, an infinite loop due to an unreachable exit condition, and an integer underflow (wraparound). The issue is fixed in version 0.25.0, and users are advised to upgrade to this version to mitigate the risk.
CVE-2026-96294 is a high-severity vulnerability in Apache Thrift's NodeJS bindings caused by uncaught exceptions and improper handling of exceptional conditions. This flaw affects all versions before 0.25.0. The issue has been fixed in Apache Thrift version 0.25.0. Users should upgrade to this version to remediate the vulnerability.
Uncaught exception, Improper Handling of Exceptional Conditions vulnerability in Apache Thrift Ruby bindings.
This issue affects Apache Thrift: before 0.25.0.
Users are recommended to upgrade to version 0.25.0, which fixes the issue.
An uncaught exception vulnerability exists in the Apache Thrift PHP bindings before version 0.25.0. This flaw can cause unhandled exceptions during execution, leading to high-severity impacts. The issue is fixed in Apache Thrift version 0.25.0, and users are advised to upgrade to this version to mitigate the risk.
CVE-2026-85493 is a high-severity vulnerability in Apache Thrift affecting versions before 0.25.0. It involves uncontrolled recursion in the Dart and Java ME bindings, which can lead to a denial of service or other impacts. The issue is fixed in version 0.25.0, and users are advised to upgrade to this version.
CVE-2026-85494 is a high-severity vulnerability in Apache Thrift affecting versions before 0.25.0. It involves improper handling of length parameter inconsistencies leading to uncaught exceptions, inefficient algorithmic complexity, excessive memory allocation, and insecure resource initialization across multiple language bindings. The issue is fixed in version 0.25.0.
CVE-2026-94639 is a high-severity vulnerability in Apache Thrift before version 0.25.0. It involves improper handling of exceptional conditions in the Java bindings, specifically allocation of resources without limits or throttling and uncaught exceptions. This flaw can lead to resource exhaustion or application instability. The issue is fixed in Apache Thrift version 0.25.0.
CVE-2026-102984 is a high-severity vulnerability in the Astro web framework prior to version 11.1.3. The @astrojs/node adapter improperly builds request URLs from the Host header, and a malformed port can cause an invalid URL. This leads to an uncaught TypeError exception before routing begins. In the default configuration, this results in an HTTP 500 response while the server continues running. However, if staticHeaders is enabled, the uncaught exception causes the Node.js process to terminate, impacting availability. The vulnerability does not expose data or allow code execution. The issue is fixed in version 11.1.3.
Improper Verification of Source of a Communication Channel in the ADS discovery of the Go implementation of Apache PLC4X (PLC4Go) allows an attacker able to send UDP datagrams to the discovering host to redirect subsequent connections to an arbitrary, attacker-chosen address. The discovery result's connection
address was derived from the AmsNetId claimed in the response body rather than from the datagram's actual source address. One spoofed discovery response can therefore insert an inventory entry pointing at any host, including hosts outside the local network, and an application that connects to discovered devices
will open its ADS session, including any configured route credentials, to that host.
Additionally, discovery listeners in both implementations can be disabled by a single malformed datagram:
- In PLC4Go ADS discovery, a short version block causes a panic that ends the listener for the rest of the discovery call, so legitimate devices answering afterwards are not reported.
- In PLC4J, the ADS and EtherNet/IP discoverers stop on an unhandled exception from a malformed response.
- The PLC4J Modbus discoverer can be made to spin indefinitely, consuming a CPU core, by a scanned host that sends a partial response.
Exploitation requires the application to invoke the discovery API, which is opt-in, and for the connection redirect, to act on the discovered items.
This issue affects Apache PLC4X: PLC4Go from 0.11.0 before 1.0.0; PLC4J ADS and Modbus drivers from 0.10.0 before 1.0.0; PLC4J EtherNet/IP driver from 0.11.0 before 1.0.0. PLC4Go is consumed as the Go module github.com/apache/plc4x/plc4go; versions refer to the corresponding Apache PLC4X releases.
Users are recommended to upgrade to version 1.0.0, which fixes the issue. Version 1.0.0 derives the connection address from the datagram's source address and logs a warning when the claimed AmsNetId disagrees with it.
CVE-2026-96274 affects the Baicells Nova 430H eNodeB (model pBS3101SH). An unauthenticated device within radio range can send a malformed uplink message with an invalid NAS payload during connection setup. The eNodeB improperly validates this payload and forwards it to the core network, causing a shutdown of the signaling association for the cell. This leads to temporary service disruption until connectivity is restored. A patch is available to address this vulnerability.
Nest is a framework for building scalable Node.js server-side applications. Prior to 11.2.4 and 12.0.2, a single message with a deeply nested object in its pattern can terminate a NestJS microservice using the TCP or RabbitMQ transport. ServerTCP#handleMessage and ServerRMQ#handleMessage pass a client-controlled non-string pattern to JSON.stringify to derive the handler lookup key; sufficiently deep nesting throws RangeError: Maximum call stack size exceeded, and the unhandled promise rejection terminates Node.js under its default behavior. An attacker who can reach the TCP port or publish to the consumed RabbitMQ queue or exchange can crash the service on demand; other transports are not affected because their patterns arrive as strings. This issue is fixed in versions 11.2.4 and 12.0.2.
setup.py test %endif
Security Fix(es):
PyJWT is a Python implementation of JSON Web Token standards. From 2.0.0a1 until 2.15.0, PyJWT PyJWKClient.get_signing_key_from_jwt is affected because payload parser catches ValueError but not RecursionError. This occurs when an attacker-controlled recursively nested payload reaches json.loads. As a result, documented PyJWT exception handling does not contain the failure. Consequently, an unauthenticated request can raise an exception that may produce an HTTP 500 response. The advisory-defined affected implementation also includes jwt/api_jwt.py, verify_signature=False. This issue is fixed in version 2.15.0.(CVE-2026-101918)
PyJWT is a Python implementation of JSON Web Token standards. From 2.13.0 until 2.14.0, PyJWS._load in jwt/api_jws.py is affected because parser catches ValueError but not RecursionError. This occurs when a deeply nested token header reaches json.loads. As a result, RecursionError escapes the documented PyJWT error hierarchy. Consequently, an unauthenticated malformed token can cause a request-level failure and HTTP 500. This issue is fixed in version 2.14.0.(CVE-2026-102265)
PyJWT is a Python implementation of JSON Web Token standards. Prior to 2.14.0, PyJWT signature segment is affected because signature segment decoding accepts characters outside the canonical Base64URL representation. This occurs when non-Base64URL characters are appended to a valid compact JWS signature segment. As a result, base64url_decode produces the same signature bytes for different serialized segments. Consequently, raw-token revocation checks can fail to recognize an equivalent modified token. This issue is fixed in version 2.14.0.(CVE-2026-102269)
PyJWT is a Python implementation of JSON Web Token standards. From 2.1.0 until 2.15.0, PyJWT OKPAlgorithm.from_jwk in jwt/algorithms.py is affected because private-JWK import path does not compare the public key derived from d with x. This occurs when an OKP private JWK supplies non-corresponding x and d components. As a result, identity derived from x can differ from operations performed with d. Consequently, if an integration also accepts private key parameters from a proof header without rejecting them, an attacker may use a stolen sender-constrained token without the legitimate private key. This issue is fixed in version 2.15.0.(CVE-2026-102275)
A vulnerability has been found in ag-ui-protocol ag-ui up to 2026-09-07. This issue affects the function JSON.parse of the file legacy/convert.ts of the component Middleware. The manipulation leads to uncaught exception. Remote exploitation of the attack is possible. Upgrading to version 2026-09-08 is capable of addressing this issue. The identifier of the patch is 30f8c794d5b73df5c610153043db502b2cc106cc. Upgrading the affected component is recommended.
CVE-2026-92608 is a high-severity vulnerability in Apache Qpid Broker-J up to version 10.1.0. It involves improper handling of property-encoding exceptions during AMQP 1.0 to AMQP 0-10 message conversion. Authenticated message producers can exploit this flaw to disrupt message delivery to AMQP 0-10 consumers. The issue is fixed in version 10.1.1.