Open Object Rexx (ooRexx) versions before 5.2.0 contain a heap buffer over-read vulnerability in the RXAPI component's QueueManager DataQueue::add method. The issue arises because the code trusts the client-supplied message.parameter1 value as the size for copying data from a heap buffer, which can lead to reading beyond the buffer boundary. An attacker can exploit this by sending a large parameter1 value in specific queue messages, potentially causing a process crash.
Nuxt versions 3.x and 4.0.0 up to but not including 4.6.4 expose the message and data of unhandled errors thrown during server rendering to clients. This occurs when errors not explicitly created as HTTP errors propagate to the error page, causing sensitive information such as internal error messages, upstream response bodies, or tokens in URLs to be included in the client-visible payload. The issue is fixed in Nuxt 4.6.4 by marking such errors as unhandled and returning generic messages instead. Nuxt 3 is end-of-life and will not receive a fix. Workarounds include catching and rethrowing errors with sanitized messages or using a Nitro plugin to hide error details. If secrets were exposed, rotation is recommended.
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, aiohttp decompresses each member of a payload containing many concatenated gzip, deflate, or zstd streams by passing the entire remaining input to a new decompressor, causing quadratic CPU use. Empty members produce no output, so client_max_size and output backpressure do not limit the work. A remote attacker can block a server event loop with a crafted compressed request body or WebSocket message, and a malicious server can similarly block a client. This issue is fixed in version 3.14.4.
Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust server memory via client-streaming or bidirectional-streaming requests.
The streaming read clause of GRPC.Server.Adapters.Cowboy.Handler.info/3 (grpc_server/lib/grpc/server/adapters/cowboy/handler.ex) asks Cowboy for up to 8,000,000 bytes per read and compares the running total with max_body_size only after the read returns. The gRPC length prefix of a message is not checked before the message is buffered. Each stream can therefore buffer up to one full read beyond the configured limit before it is refused, and many concurrent streams exhaust node memory. Releases before 1.0.6 apply no limit to streaming requests at all.
This issue affects grpc_server: from 1.0.0 before 1.1.0.
Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in elixir-grpc grpc_server and grpc allows unauthenticated attackers to occupy a BEAM scheduler indefinitely via a client-streaming or bidirectional-streaming request whose body ends inside a gRPC message.
GRPC.Server.Adapters.Cowboy.read_stream/1 (grpc_server/lib/grpc/server/adapters/cowboy.ex, and the Cowboy adapter in grpc before the package split) asks for more data whenever the buffer does not hold a complete message. Once the request body has ended, every further read returns an empty chunk, so the buffer never changes and the function retries without end. A single 5-byte length prefix sent with END_STREAM keeps one scheduler busy for as long as the connection stays open, and repeated requests exhaust all schedulers.
This issue affects grpc: from 0.3.1 before 1.0.0; grpc_server: from 1.0.0 before 1.1.0.
A vulnerability identified as CVE-2026-125332 affects Microsoft product version 3.0, where the TLS client crashes upon receiving a ServerHello message with an unsupported compression method. This issue relates to improper input validation (CWE-20). No CVSS score or detailed impact information is provided.
Multiple security vulnerabilities have been identified in libsoup3, an HTTP library used by GNOME applications for asynchronous HTTP access. These include remote denial of service issues via WebSocket protocol violations and unbounded decompression, as well as several heap buffer overflows and use-after-free conditions affecting HTTP/2 client and WebSocket message handling. Red Hat has issued an important security update addressing these issues in Red Hat Enterprise Linux 10.
Multiple critical security vulnerabilities have been identified and fixed in FreeRDP, a free implementation of the Remote Desktop Protocol client. These include remote code execution, information disclosure, denial of service, use-after-free, heap buffer overflows, and protocol negotiation bypass issues affecting FreeRDP versions prior to 3.32.2. The vulnerabilities impact various components such as freerdp-proxy, protocol negotiation, channel message handling, and clipboard processing. Red Hat has released an update for Red Hat Enterprise Linux 10 rebased to FreeRDP version 3.32.2 or newer to address these issues.
A vulnerability in the DNS-over-QUIC (DoQ) server component of hickory-server (hickory-dns) before version 0.26.2 allows remote unauthenticated clients to open a connection and keep a request stream open indefinitely. This occurs because the server does not apply any timeout when reading a request message from a QUIC stream, bypassing all configured timeouts. This can lead to resource exhaustion and denial of service on the affected server.
Allocation of Resources Without Limits or Throttling vulnerability in elixir-grpc grpc_server allows unauthenticated attackers to exhaust memory and crash the node via an oversized client-streaming or bidirectional-streaming request body.
The streaming read clause of 'Elixir.GRPC.Server.Adapters.Cowboy.Handler':info/3 (grpc_server/lib/grpc/server/adapters/cowboy/handler.ex) never checks the configured max_body_size. Only the unary read path enforces that cap. 'Elixir.GRPC.Server.Adapters.Cowboy':reading_stream/1 (grpc_server/lib/grpc/server/adapters/cowboy.ex) appends every received chunk to its buffer until a complete length-prefixed message arrives. A client can declare a very large message and send it across many small HTTP/2 DATA frames, and the server buffers all of it.
This issue affects grpc_server: from 1.0.0 before 1.0.6.
A flaw was found in D-Bus. With a privileged Monitoring client attached (for example dbus-monitor or busctl monitor), an unprivileged local user can cause dbus-daemon to abort if a driver-originated broadcast such as NameOwnerChanged or ActivatableServicesChanged cannot be delivered to a recipient (for example due to a deny rule or an exceeded outgoing message queue). Driver broadcasts still use serial 0; when delivery fails, composing the monitor error reply asserts reply_serial != 0 and aborts the daemon.
FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, rtmp_i_connect() passed the first RTMP connect argument to amf0_object_get() without checking whether the AMF value was an object. A string or number in place of an AMF object caused union bytes from the message to be interpreted as node pointers and dereferenced. Any client with network access to an enabled mod_rtmp listener could send the malformed connect command before login; the module is disabled in the stock build and configuration. The invalid read reliably crashes FreeSWITCH and ends every active call, while no write, memory disclosure, or code execution has been demonstrated. This issue is fixed in version 1.11.2.
FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, mod_event_socket used an unauthenticated Content-Length value directly as the allocation size for an Event Socket message body. Negative or extremely large values could overflow the terminator calculation or force an allocation failure through a helper that aborts the FreeSWITCH process. The header is parsed before the Event Socket password, so any host admitted by apply-inbound-acl can trigger termination with its first packet; the default loopback ACL limits ordinary installations to local clients. The outbound socket dialplan path is also affected when FreeSWITCH connects to a hostile application server, and process termination drops every active call until the service is restarted. This issue is fixed in version 1.11.2.
FreeSWITCH is a Software Defined Telecom Stack enabling the digital transformation from proprietary telecom switches to a software implementation that runs on any commodity hardware. Prior to 1.11.2, rtmp_rtmp2rtpH264() trusted the length prefix of each inbound H.264 NAL unit without checking it against the bytes remaining in the RTMP message. An oversized declared unit underflowed the unsigned remaining-byte counter and advanced the parser beyond its receive buffer, where the next length-prefix read could crash the process. The flaw affects deployments that build and load mod_rtmp and accept video call sessions, commonly on TCP port 1935; placing the call requires a directory login where auth-calls is true, while no credentials are required where auth-calls is absent or false. A remote client can terminate FreeSWITCH and every active call, but the defect supplies no write primitive and memory disclosure has not been demonstrated. This issue is fixed in version 1.11.2.
FreeRDP versions from 3.0.0 up to but not including 3.32.2 contain a vulnerability in the proxy component that allows connected clients to cause uncontrolled resource consumption. This occurs through intercepted Dynamic Virtual Channel (DVC) message reassembly, where attackers can declare a large DATA_FIRST length and send incomplete fragments, causing heap memory to grow proportionally to traffic and degrade service availability.