PULSE
FEED
ransomeverest reclama a FAST ČR · CZ · Government & Defenseransomeverest reclama a Alla France · FR · Otherransomeverest reclama a ABL Bio · Healthcareransomeverest reclama a Vizrt · NO · Technologyransomeverest reclama a ALKFransomeverest reclama a Geesol · Technologyransomeverest reclama a My American Alliance · Otherransomeverest reclama a Accuver · Technologyransomwhitearmor reclama a DROP 1 — ALL FOUR CLINICS — 8,000 PATIENTS, 4,000 INVOICES, 7,733 CREDENTIALS · Healthcareransomdark project reclama a VanMor · CA · Otherransomeverest reclama a KOWA · JP · Healthcareransomeverest reclama a Rays Power Infra · IN · Energy & Utilitiesransomrhysida reclama a BK Law Group LLC · US · Professional Servicesransomaurora reclama a Calvatis GmbH · DE · Professional Servicesransomeverest reclama a FAST ČR · CZ · Government & Defenseransomeverest reclama a Alla France · FR · Otherransomeverest reclama a ABL Bio · Healthcareransomeverest reclama a Vizrt · NO · Technologyransomeverest reclama a ALKFransomeverest reclama a Geesol · Technologyransomeverest reclama a My American Alliance · Otherransomeverest reclama a Accuver · Technologyransomwhitearmor reclama a DROP 1 — ALL FOUR CLINICS — 8,000 PATIENTS, 4,000 INVOICES, 7,733 CREDENTIALS · Healthcareransomdark project reclama a VanMor · CA · Otherransomeverest reclama a KOWA · JP · Healthcareransomeverest reclama a Rays Power Infra · IN · Energy & Utilitiesransomrhysida reclama a BK Law Group LLC · US · Professional Servicesransomaurora reclama a Calvatis GmbH · DE · Professional Services
← Todos os CVEs
CVE Watch10 de nov. de 2026

CVE-2026-21441

urllib3 is an HTTP client library for Python. urllib3's streaming API is designed for the efficient handling of large HTTP responses by read

CVSS

7.5

Alta

EPSS

2.9%

p87

KEV

—

Exploit Today

26

0-100

Publicado: 7 de jan. de 2026 · Última mod.: 10 de nov. de 2026 · CWE-409

EPSS · 30d
2.9%EPSS · 30 dias2.9%
2026-10-232026-11-19
Descrição técnica

urllib3 is an HTTP client library for Python. urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once. urllib3 can perform decoding or decompression based on the HTTP `Content-Encoding` header (e.g., `gzip`, `deflate`, `br`, or `zstd`). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption. Starting in version 1.22 and prior to version 2.6.3, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client. Applications and libraries are affected when they stream content from untrusted sources by setting `preload_content=False` when they do not disable redirects. Users should upgrade to at least urllib3 v2.6.3, in which the library does not decode content of redirect responses when `preload_content=False`. If upgrading is not immediately possible, disable redirects by setting `redirect=False` for requests to untrusted source.

Referências oficiais
CVEs relacionados
CVECVSSEPSSKEVRExploitTítuloMod.
CVE-2026-1336085.3 MÉD
—
———A vulnerability was identified in OpenZipkin Zipkin 3.6.1. This affects the function UnzippingBytesRequestConverter.convertRequest of the file zipkin-server/src/main/java/zipkin2/server/internal/ZipkinHttpCollector.java of the component HTTP Collector. Such manipulation leads to highly compressed data. The attack can be executed remotely. The pull request to fix this issue awaits acceptance.14h
CVE-2026-103025—
—
——0bep/imagemeta is a Go library for reading EXIF, IPTC and XMP image meta data from JPEG, TIFF, PNG, and WebP files. Prior to 0.17.3, imagemeta.Decode could exhaust memory when parsing PNG zTXt chunks whose keyword is "Raw profile type iptc": the declared chunk length can drive an allocation far larger than the input file, and the embedded zlib stream is decompressed without an output limit. The advisory reports a 42-byte input causing a 256 MB allocation and a 127 KB input inflating to 460 MB. The oversized-allocation path's memory effect depends on platform overcommit and configured GOMEMLIMIT or cgroup limits, while the decompression path reliably creates resident memory. Applications that decode untrusted PNGs with IPTC metadata processing can therefore suffer denial of service through memory exhaustion. This issue is fixed in 0.17.3.1d
CVE-2026-130091—
41.6%
——12A caller with write permission in a namespace can terminate temporal-proxy through memory exhaustion by storing highly compressed payloads in Workflow history, and the stored history causes the same failure on every later read. temporal-proxy 1.2.0 decompresses every payload marked as compressed in the responses it forwards, whether or not compression is configured. Each payload is limited to 4 MiB after decompression, but the total for a response is not, and the decoded payloads are held in memory together. The caller can store many small, highly compressed payloads through the proxy or directly at the upstream Temporal service. When that history is read through the proxy, for example by a Worker processing a task, the proxy can run out of memory and be terminated. The codec server's /decode endpoint is affected in the same way when it is enabled. Only temporal-proxy 1.2.0 is affected; earlier versions do not decompress payloads. The issue is fixed in 1.2.1. Upgrade to 1.2.1 or later.2d
CVE-2026-121808—
54.0%
——16Improper Handling of Highly Compressed Data (Data Amplification) vulnerability in elixir-grpc grpc_core and grpc allows unauthenticated attackers to exhaust server memory via a compressed Erlang external term in a gRPC message body. GRPC.Codec.Erlpack.decode/2 (grpc_core/lib/grpc/codec/erlpack.ex, and lib/grpc/codec/erlpack.ex before the package split) passes the message body to :erlang.binary_to_term/2. That function inflates a compressed term in full before it returns. The codec sets no limit on the decoded size, and its type checks run only on the decoded term. The server's max_body_size limit counts the compressed bytes of the request. A request with Content-Type: application/grpc+erlpack can therefore make the server allocate a term much larger than the request body. This issue affects grpc: from 0.4.0 before 1.0.0; grpc_core: from 1.0.0 before 1.1.0.21h
CVE-2026-777066.5 MÉD
14.6%
——4Improper handling of highly compressed data (data amplification) vulnerability in Fileorbis Bilişim Hizmetleri Ticaret Anonim Şirketi FileOrbis NextGen FileServer allows Sustained Client Engagement. This issue affects FileOrbis NextGen FileServer: before 12.7.4d
CVE-2026-1282427.5 ALT
61.4%
——18actix-http before 3.20.1 and actix-web before 4.18.2 contain an unbounded decompression vulnerability in encoding::Decoder that lets remote attackers exhaust memory and CPU via compressed bodies. Attackers can send small highly compressed gzip, deflate, Brotli or zstd request bodies to Json, Form, Bytes or String extractors, or serve them to awc clients, causing denial of service.7d