Description
Zapros, a Python HTTP client, prior to version 0.14.0 is vulnerable to denial of service via memory exhaustion. The issue affects all callers who streamed compressed responses relying on the chunk size — explicit (`iter_bytes(chunk_size=...)`) or the default — to bound memory. The decoder ignored that bound, so a chunk could be far larger than requested and a single compressed response could overflow memory. Version 0.14.0 contains a patch. Some workarounds are available. Read the still-compressed body with `Response.iter_raw()` / `Response.async_iter_raw()`, which bypass the built-in decoders, and decompress it yourself with an explicit output-size bound (e.g. `zlib`'s `max_length`), aborting once a configured limit is exceeded. Where feasible, send `Accept-Encoding: identity` to disable response compression so bodies are not decompressed client-side. Avoid decoding response bodies from untrusted servers.
Published: 2026-09-21
Score: 8.7 High
EPSS: n/a
KEV: No
Impact: Denial of Service via memory exhaustion
Action: Immediate Patch
AI Analysis

Impact

Zapros, a Python HTTP client, is susceptible to a denial‑of‑service flaw when it streams compressed responses. The streaming decoders ignore the requested chunk size, allowing an attacker to send a single compressed chunk that vastly exceeds the expected size. This results in unbounded memory allocation, exhausting system RAM and causing the client to crash or become unresponsive. The weakness is an unchecked allocation based on input data, classic buffer‑size overflow (CWE‑770).

Affected Systems

The Zapros HTTP client from kap-sh is affected for all releases before version 0.14.0, including those that use the default or explicit chunk‑sized streaming API. All calls that rely on the client’s automatic decompression will be impacted unless the caller opts to bypass the built‑in decoder.

Risk and Exploitability

The vulnerability is rated 8.7 on the CVSS scale; it is a high‑severity denial‑of‑service flaw. No EPSS data is available and the flaw is not listed in CISA’s KEV catalog. The likely attack vector is a remote malicious server that sends a decompressed response compressed with a large chunk size to an instance of Zapros. When the client attempts to stream that response, it will allocate unbounded memory, potentially exhausting system resources and rendering the client (or host) unusable. Given the missing EPSS data, the exploitation probability remains uncertain but the impact is severe for any affected deployment.

Generated by OpenCVE AI on September 21, 2026 at 22:40 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade Zapros to version 0.14.0 or newer, which applies the necessary bounds to streaming decoders.
  • If an upgrade is not immediately possible, bypass the built‑in decoders by reading the response with Response.iter_raw() or Response.async_iter_raw(), then decompress manually using a library such as zlib with a maximum output size specified and abort when the limit is exceeded.
  • Set the request header Accept‑Encoding to identity to disable server‑side compression, ensuring the client never performs remote decompression of untrusted data.
  • Avoid decoding compressed responses from untrusted servers whenever possible.

Generated by OpenCVE AI on September 21, 2026 at 22:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 21 Sep 2026 21:30:00 +0000

Type Values Removed Values Added
Description Zapros, a Python HTTP client, prior to version 0.14.0 is vulnerable to denial of service via memory exhaustion. The issue affects all callers who streamed compressed responses relying on the chunk size — explicit (`iter_bytes(chunk_size=...)`) or the default — to bound memory. The decoder ignored that bound, so a chunk could be far larger than requested and a single compressed response could overflow memory. Version 0.14.0 contains a patch. Some workarounds are available. Read the still-compressed body with `Response.iter_raw()` / `Response.async_iter_raw()`, which bypass the built-in decoders, and decompress it yourself with an explicit output-size bound (e.g. `zlib`'s `max_length`), aborting once a configured limit is exceeded. Where feasible, send `Accept-Encoding: identity` to disable response compression so bodies are not decompressed client-side. Avoid decoding response bodies from untrusted servers.
Title Zapros: Streaming decoders ignored the requested chunk size, allowing a single compressed response chunk to allocate unbounded memory (decompression bomb)
Weaknesses CWE-770
References
Metrics cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-21T21:13:26.969Z

Reserved: 2026-07-10T18:25:21.466Z

Link: CVE-2026-61652

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-21T22:16:57.680

Modified: 2026-09-21T22:16:57.680

Link: CVE-2026-61652

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-21T22:45:17Z

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling