RabbitMQ is a messaging and streaming broker. Prior to versions 4.2.7 and 4.3.1, The stream open handler calls only check_vhost_access; it omits the node/vhost/user connection-limit checks that rabbit_reader performs for AMQP. A developer %% FIXME comment at the cited line explicitly acknowledges the gap. No compensating enforcement exists in connection tracking or elsewhere in rabbitmq_stream. An authenticated tenant can fully bypass operator-configured per-user and per-vhost connection caps by connecting via port 5552 instead of 5672. Preconditions include rabbitmq_stream plugin enabled Authenticated stream-protocol credentials Operator relies on per-user/per-vhost connection limits for tenant isolation. This issue is fixed in versions 4.2.7 and 4.3.1.
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6, parse_array_primitive/2 for constructor 0x45 (list0) returns an element with byte-width B = 0. The enclosing array32 parser at line 148 reads a 4-byte Count from the wire and loops Count times consuming B bytes each , with B = 0, no input is consumed and the loop builds a list of Count empty elements bounded only by the 32-bit field. The SASL-mechanisms / SASL-init frame is parsed by amqp10_framing:decode_bin/1 from rabbit_amqp_reader.erl:412 before authentication completes. The pre-auth incoming_max_frame_size (default 8192 bytes) caps the frame, not the Count field, so a 19-byte payload with Count = 0xFFFFFFFF is accepted. No max_heap_size is set on the reader process. An unauthenticated network attacker can crash any RabbitMQ node that has the AMQP 1.0 listener enabled (default port 5672) by sending a single ~19-byte frame. The reader process attempts to build a list of ~4 billion empty elements, exhausting heap memory and terminating the Erlang VM. All tenants and protocols on the node lose service. Preconditions include Network reachability to the AMQP listener (port 5672, enabled by default) No authentication required. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, and 4.2.6.
CVE-2026-92284 is a medium severity vulnerability in caddyserver's caddy platform versions 2.11.3 and earlier. It involves unbounded memory allocation when resolving http.request.body in the replacer.go module, which reads the entire request body before middleware limits apply. This can lead to memory exhaustion and process termination.
Jawn is an open source JSON parser that prior to version 1.7.0 allowed parsing of JSON with arbitrarily deep nesting without limits. This could cause the parser to exhaust the JVM heap memory, resulting in a fatal OutOfMemoryError and denial of service. The issue is fixed in version 1.7.0.
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the default-open GET /subscribe endpoint in network/api/websocket/routes.go accepts unauthenticated WebSocket clients with permissive origin handling, does not call SetReadLimit to bound message size, and has no live-connection cap. SocketHub.HandleClientInsertion also accepts an unbounded address list that grows addressSubscription, and client.loopIn continues reading without a size limit, allowing one client to grow subscription maps or many clients to retain goroutines, buffered channels, and descriptors. The global HTTP request throttler does not count upgraded live WebSocket connections. Because the REST and WebSocket API runs in the node process, memory or scheduler exhaustion can crash the node and interrupt P2P and consensus participation. This issue is fixed in version 1.7.20.
Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, the broker does not enforce a maximum length for pending per-session message queues. When a fast publisher sends messages to a slow subscriber whose in-flight window is full, queued messages can accumulate without bound in memory or persistent storage. Remote clients can use this condition to exhaust broker resources and cause a denial of service. This issue is fixed in version 0.18.1.
CVE-2026-96609 is a resource allocation vulnerability in Robur Albatross versions 1.0.0 through 2.x before 2.7.2. The product does not limit the use of its ring buffer, which can lead to an infinite loop in the albatross-console when processing console subscription commands that generate sufficient log output. Exploitation requires user privileges to send these commands and is not possible by unauthorized clients.
CVE-2026-78383 is a high severity vulnerability in Apache Tomcat involving allocation of resources without limits or throttling. It allows an unauthenticated AJP request to pin an AJP processing thread, causing denial of service. Affected versions include Apache Tomcat from 11.0.0-M1 through 11.0.25, 10.1.0-M1 through 10.1.59, 9.0.0.M1 through 9.0.121, and some older EOL versions. Upgrading to versions 11.0.26, 10.1.60, or 9.0.122 mitigates the issue.
CVE-2026-89425 is a high-severity vulnerability in FasterXML jackson-core affecting versions from 2.8.0 through 3.2.2 in various subranges. The issue arises in UTF8DataInputJsonParser._reportInvalidToken(), which accumulates malformed token text without any upper bound, leading to excessive memory use. This can cause the Java Virtual Machine to run out of memory and crash due to unbounded StringBuilder growth when processing large malformed tokens via the DataInput parsing path.
IBM Financial Transaction Manager (FTM) for RedHat OpenShift could allow a remote attacker to cause a denial of service due to allocation of resources without limits or throttling.
IBM Concert 1.0.0 through 3.0.0 could allow a remote attacker to cause a denial of service using a specially crafted regular expression that would cause excessive resource consumption.
CVE-2026-81886 is a medium severity vulnerability in radare2 prior to version 6.2.0. It involves the Windows 64-bit crash-dump dmp64 parser, which improperly uses an input-controlled PageCount to allocate memory without validating against the dump size. This can lead to excessive memory consumption and processing time, causing a denial of service. The issue is fixed in radare2 version 6.2.0.
CVE-2026-81885 is a medium severity vulnerability in radare2 prior to version 6.2.0. The issue involves the NE relocation fixup-chain parser, which lacks iteration limits or cycle detection when processing relocation entries. An attacker can trigger a denial of service by opening a crafted NE executable that causes the parser to repeatedly allocate resources indefinitely, leading to excessive CPU and memory consumption. This vulnerability is fixed in radare2 version 6.2.0.
CVE-2026-94455 is a vulnerability in GitroomHQ's postiz-app allowing unauthenticated creation of enterprise organizations with elevated privileges. The affected HTTP endpoint lacks proper authentication checks, relying solely on a token signed with the instance secret but not verifying token purpose or expiry. This flaw permits an attacker with a valid user session token to create a new organization with the highest subscription tier and obtain its API key, which is immediately valid for API access.
Allocation of Resources Without Limits or Throttling vulnerability in Erlang/OTP ssh allows an authenticated remote attacker to exhaust node memory by repeatedly opening session channels that are never assigned a handler.
The "session" clause of ssh_connection:handle_msg/4 checks only minimal_remote_max_packet_size before calling setup_session/5, which unconditionally builds a #channel{} record and stores it in the ETS channel cache. The max_channels daemon option is consulted only by ssh_channel_sup:max_num_channels_not_exceeded/2, which counts supervisor children, so a channel that never gets a shell, exec, or subsystem handler is invisible to the limit and setting the option to a finite value does not mitigate the attack. RFC 4254 section 5.1 permits many session channels per connection, and each record costs only a few hundred bytes, so a single authenticated connection can accumulate channels until the node runs out of memory and the emulator terminates, affecting every application on it. No file contents, credentials, or write access are obtainable.
This issue affects OTP from OTP 18.1.2 before OTP 27.3.4.18, OTP 28.5.0.7, and OTP 29.1.1, corresponding to ssh from 4.1.1 before 5.2.11.13, 5.5.2.6, and 6.0.6. Whether OTP before OTP 18.1.2, corresponding to ssh before 4.1.1, is affected is unknown.
Zapros, a Python HTTP client, prior to version 0.14.0 is vulnerable to denial of service when an application requests content from an untrusted server, or follows a redirect to one, because a malicious response containing an excessive number of chained `Content-Encoding` values causes Zapros to construct a deeply nested decompression chain that consumes excessive resources. Version 0.14.0 patches the vulnerability by limiting responses to five content-encoding layers and raising `DecodingError` when that limit is exceeded. As a workaround, applications can add response middleware that inspects the `Content-Encoding` header and rejects responses containing more than a safe number of encoding layers.
Zapros, a Python HTTP client, has a denial of service vulnerability prior to version 0.14.0 caused by memory exhaustion when processing compressed HTTP responses. The issue arises because the decoder does not respect the chunk size limit, allowing a single compressed response to consume excessive memory. Version 0.14.0 includes a patch to address this vulnerability. Workarounds include manually decompressing the response with explicit output-size limits or disabling compression by sending the Accept-Encoding: identity header.
CVE-2026-85219 is a denial-of-service vulnerability in the Redis module of Thinkst Applied Research's OpenCanary version 0.9.9 and earlier. It allows an unauthenticated remote attacker to cause unconstrained memory usage by allocating resources without limits or throttling. The vulnerability has a low severity rating with a CVSS score of 3.7. No official patch or remediation information is provided in the available data.
nginx ignition is a user interface for the nginx web server. In versions 2.29.0 through 2.40.0, the gin i18n middleware in nginx-ignition's API server runs in front of every HTTP request and calls `golang.org/x/text/language.ParseAcceptLanguage` on the raw `Accept-Language` header without imposing any size or shape filter. The underlying parser has quadratic-time behaviour on long lists of malformed language tags. The CVE-2022-32149 guard that golang.org/x/text added in v0.3.8 caps the number of `-` characters in the input at 1000, but it does not cap `_` characters even though the parser's internal scanner aliases `_` to `-` before parsing. A single unauthenticated GET request with an `Accept-Language` header built out of `_` separators burns about 2.4 seconds of server CPU on the host running nginx-ignition; ten concurrent attackers saturate a ten-core box for the duration of the attack while consuming ~10 MiB/s of upstream bandwidth. Version 2.40.1 fixes this issue.