PULSE
FEED
ransomqilin reclama a Hocon Gas · NG · Energy & Utilitiesransomqilin reclama a HyperGen · US · Technologyransomqilin reclama a Chattanooga Shooting Supplies · US · Retail & E-Commerceransomqilin reclama a Brame Telecom · BR · Technologyransomiah6477 reclama a hensley · Otherransomvexy ransomware reclama a Enchanted Fine Jewellery · IN · Retail & E-Commerceransomiah6477 reclama a buckle · Retail & E-Commerceransomiah6477 reclama a camden-living · GB · Hospitalityransomemperador reclama a MPI LTDA · BR · Otherransomspacebears reclama a Alma Center Servizi Medicali S.r.l. · IT · Healthcareransomspacebears reclama a Holistic Health Group, Inc. (d/b/a Suncrafted) · US · Healthcareransomn0n reclama a Company #69 · Not Foundransomiah6477 reclama a alera · Professional Servicesransomn0n reclama a Company #68 · US · Not Foundransomqilin reclama a Hocon Gas · NG · Energy & Utilitiesransomqilin reclama a HyperGen · US · Technologyransomqilin reclama a Chattanooga Shooting Supplies · US · Retail & E-Commerceransomqilin reclama a Brame Telecom · BR · Technologyransomiah6477 reclama a hensley · Otherransomvexy ransomware reclama a Enchanted Fine Jewellery · IN · Retail & E-Commerceransomiah6477 reclama a buckle · Retail & E-Commerceransomiah6477 reclama a camden-living · GB · Hospitalityransomemperador reclama a MPI LTDA · BR · Otherransomspacebears reclama a Alma Center Servizi Medicali S.r.l. · IT · Healthcareransomspacebears reclama a Holistic Health Group, Inc. (d/b/a Suncrafted) · US · Healthcareransomn0n reclama a Company #69 · Not Foundransomiah6477 reclama a alera · Professional Servicesransomn0n reclama a Company #68 · US · Not Found
← Todos los CVEs
CVE Watch13 oct 2026

CVE-2026-96618

Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in hexpm hex allows an untrusted package mirror to exhaust th

CVSS

—

Sin CVSS

EPSS

0.3%

p24

KEV

—

Exploit Today

7

0-100

Publicado: 12 oct 2026 · Última mod.: 13 oct 2026 · CWE-409 · CWE-770

EPSS · 30d
0.3%EPSS · 30 días0.3%
2026-10-132026-10-14
Descripción técnica

Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in hexpm hex allows an untrusted package mirror to exhaust the memory or disk space of the machine running mix deps.get, mix deps.update, mix hex.package fetch or mix hex.docs fetch. Hex treats a mirror configured with HEX_MIRROR_URL, HEX_MIRROR or mirror_url as untrusted: it doesn't send credentials to it, and it checks registry signatures and package checksums that the mirror can't forge. Several response paths consume memory or disk in proportion to what the mirror sends before any of those checks run. Hex.HTTP.request/5 reads the whole response body into memory and decompresses it with :zlib.gunzip/1 whenever the response's Content-Encoding contains gzip, with no limit on the compressed or decompressed size. Hex doesn't ask for compressed responses, so the server decides whether this step runs. It applies to registry, package, docs and API responses. Package tarballs have no download size limit. Hex 2.5.1 holds the whole tarball in memory and writes it to the cache, and the development branch streams it to a temporary file; the 16 MiB tarball limit is checked only when the file is unpacked. The tarball is then unpacked, into deps/<app> in 2.5.1 and into a staging directory on the development branch, before its checksums are compared with the registry. mix hex.docs fetch, and mix hex.docs offline when docs are missing, write the docs tarball to disk and extract it with :mix_hex_erl_tar.extract/2 without the 16 MiB compressed and 128 MiB decompressed limits that mix_hex_tarball:unpack_docs/3 applies. The signed registry doesn't cover docs tarballs, so nothing checks them. Registry responses are also decompressed before their signature is checked, in hex_core code that Hex vendors; that part is tracked in https://github.com/hexpm/hex_core/security/advisories/GHSA-7c4r-cgf9-9jmq. This issue affects hex: from 0.11.2 before 2.5.2.

Referencias oficiales
CVEs relacionados
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-110726—
—
———In `api-gateway` versions till `1.7.3`, The default rate-limit key resolver, `ClientIpKeyResolver`, derives the per-client bucket key from the leftmost element of the `X-Forwarded-For` request header. That element is supplied by the originating HTTP client and is not validated against any trusted-proxy list. A single attacker can therefore obtain an unlimited number of independent rate-limit buckets — one per unique header value — and completely bypass the gateway's request-rate limiting on every route that uses the shipped default configuration.5h
CVE-2026-110843—
—
——0n8n before 2.41.4 and 2.42.x before 2.42.1 contains an uncontrolled resource consumption vulnerability in the unauthenticated OAuth authorize endpoint, which resolves clients by URL path but stores the caller's raw identifier as the record key. Unauthenticated attackers can send identifiers differing only in their query string to create unlimited first-party client records that bypass the registration cap, growing the database until the disk fills.18h
CVE-2026-1026825.6 MED
—
——0Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents. From 0.0.98 until 1.6.0, the pipecat-ai package's built-in development runner exposes unauthenticated endpoints including /start, /daily, and /daily-dialin-webhook that can create bot sessions and Daily rooms. The runner binds to localhost by default and is intended only for local development, so exploitation requires an operator to expose it to untrusted traffic through --host 0.0.0.0, a published port, or a tunnel without access controls. An unauthenticated caller can consume local resources and third-party quotas and, depending on configuration, receive a room URL and join token. Version 1.6.0 adds a prominent development-runner banner and documentation that clarifies the unauthenticated boundary and directs production deployments to an authenticated dispatcher or managed runtime, while the endpoint behavior remains by design. This issue is fixed in version 1.6.0.22h
CVE-2026-1095277.5 ALT
—
——0The Model Context Protocol Python SDK is the official Python SDK for Model Context Protocol servers and clients. In mcp versions before 1.29.1 and from 2.0.0a1 through 2.0.1, the Streamable HTTP session manager, SSE message endpoint, and OAuth authorization-server routes buffer complete HTTP request bodies without enforcing a maximum size. An unauthenticated remote client able to reach an affected endpoint can send a large declared or streamed request body that consumes multiple times the body size in process memory and can repeatedly exhaust memory or terminate the server. Stdio-only servers and deployments with an effective upstream request-size limit are not affected, and applications that use StreamableHTTPServerTransport directly remain responsible for enforcing their own limit. The standard SDK server applications and session managers are fixed in versions 1.29.1 and 2.1.0.23h
CVE-2026-1083957.5 ALT
—
——0The Model Context Protocol Java SDK is the official Java SDK for Model Context Protocol servers and clients. From version 0.8.0 through 0.12.0 in the io.modelcontextprotocol.sdk:mcp artifact, from 0.13.0 through 0.18.3 and 1.0.0 through 1.1.3 in io.modelcontextprotocol.sdk:mcp-core, and from mcp-core 2.0.0-M1 through 2.0.0, the Servlet-based SSE, Streamable HTTP, and Stateless server transports read an HTTP request body into memory without enforcing a maximum size. An unauthenticated remote client able to reach an affected transport can stream an arbitrarily large POST body, including with chunked transfer encoding, until the Java process exhausts its heap and becomes unavailable. Authentication, Origin or Host validation, or an upstream request-size limit can reject the request before the vulnerable read. The maintained mcp-core lines are fixed in versions 0.18.4, 1.1.4, and 2.0.1.21h
CVE-2026-1020726.5 MED
—
——0An Improper Handling of Highly Compressed Data vulnerability in the gRPC library used by na-grpcd of Juniper Networks Junos OS allows an authenticated network-based attacker to cause a denial of service via a compressed gRPC request.20h