CVE-2023-5685
A flaw was found in XNIO. The XNIO NotifierState that can cause a Stack Overflow Exception when the chain of notifier states becomes problem
CVSS
7.5
Alta
EPSS
3.5%
p89
KEV
—
Exploit Today
27
0-100
Publicado: 22 de mar. de 2024 · Última mod.: 4 de nov. de 2026 · CWE-400
3.5%EPSS · 30 dias3.5%
2026-10-192026-11-16
A flaw was found in XNIO. The XNIO NotifierState that can cause a Stack Overflow Exception when the chain of notifier states becomes problematically large can lead to uncontrolled resource management and a possible denial of service (DoS).
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2023:7637
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2023:7638
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2023:7639
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2023:7641
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2024:10207
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2024:10208
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2024:2707
- access.redhat.comhttps://access.redhat.com/security/cve/CVE-2023-5685
- bugzilla.redhat.comhttps://bugzilla.redhat.com/show_bug.cgi?id=2241822
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2023:7637
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2023:7638
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2023:7639
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2023:7641
- access.redhat.comhttps://access.redhat.com/errata/RHSA-2024:2707
- access.redhat.comhttps://access.redhat.com/security/cve/CVE-2023-5685
- bugzilla.redhat.comhttps://bugzilla.redhat.com/show_bug.cgi?id=2241822
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-1293027.5 ALT—
——0Guard Core is an API security core engine for the FastAPI-Guard, FlaskAPI Guard, and DjAPI Guard adapters. From 3.5.0 until 3.13.0, built-in penetration-detection patterns in guard_core/handlers/suspatterns_handler.py execute through a direct pattern.search(content) call instead of the timeout-protected create_safe_matcher() path used for custom patterns. The built-in template-injection detector contains an unbounded expression with quadratic behavior when scanning repeated opening braces. Because penetration detection and enhanced mode are enabled by a stock SecurityConfig, an unauthenticated request can block the shared asyncio event loop, affecting all application endpoints. The triggering input does not produce a detection match, so the request can complete without incrementing ban counters or being recorded as suspicious. This issue is fixed in version 3.13.0.18hCVE-2026-1288425.3 MÉD—
——0@fastify/busboy is a streaming parser for multipart and url-encoded form data used by Fastify. In versions 1.0.0 through 3.2.5, the url-encoded parser stops accumulating a field only when the decoded length exactly equals the configured per-field size limit, and a malformed percent escape is passed through verbatim by the decoder, so the decoded length can jump from just below the limit to just above it and skip that equality check. The parser then keeps buffering the field in memory until the next delimiter or the end of the request, so a single unauthenticated url-encoded field or field name can grow to the size of the whole request body regardless of a much smaller configured per-field limit, with memory use bounded only by the independent whole-request body limit. The issue is fixed in @fastify/busboy 3.2.6, which clamps a field as soon as the decoded length reaches or exceeds the limit, and users should upgrade to 3.2.6 or later. As a workaround, set a conservative whole-request body limit so the per-field overshoot cannot exceed it.17hCVE-2026-1288357.5 ALT—
——0@fastify/busboy is a streaming parser for multipart form data used by Fastify. In versions 1.0.0 through 3.2.5, a multipart part whose header block is never terminated before the next boundary is counted by the vendored Dicer parser as an open part that never ends, so the parser emits neither a finish nor an error event and the request hangs. A single unauthenticated request of roughly one hundred bytes triggers the stall, and through @fastify/multipart the hung handler is not released when the client disconnects, so repeated requests leak handlers and whatever resources they hold, such as files, database connections and concurrency slots, until the process is restarted. The same parser is reached by the formData methods of undici versions 5.25.3 through 6.7.0. The issue is fixed in @fastify/busboy 3.2.6, and users should upgrade to 3.2.6 or later. As a workaround, configure Fastify's handler timeout so hung handlers are eventually terminated and their resources released.17hCVE-2026-128132—39.0%
——12AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the WebSocket reader continues parsing frames already received after the receive queue pauses the transport, and empty messages are not counted toward the queue size. With permessage-deflate, one read of compressed frames can add many megabytes of decompressed messages to the receive queue. A remote peer can send many small or compressed messages faster than the application consumes them and cause excessive memory use in a server or client. This issue is fixed in version 3.14.4.4dCVE-2026-128131—44.7%
——13AIOHTTP 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.22hCVE-2026-128127—46.3%
——14AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, BodyPartReader.read_chunk() processing a multipart part with Content-Transfer-Encoding set to base64 keeps reading until the chunk length is a multiple of four without enforcing a byte limit. A short Content-Length or a long run of whitespace can cause one call to read the remaining body into memory before the size check or spin on the event loop. A remote attacker can send such a multipart request to a handler that reads multipart data and bypass client_max_size. This issue is fixed in version 3.14.4.22h