Vulnerability in zapros (CVE-2026-61652)
Summary
Vulnerability in zapros (CVE-2026-61652). Risk of unauthorized operations or information disclosure. Exploitable via chunk. Mitigation: upgrade to 0.14.0 or later.
Original description
The description as published by the source.
Impact
Denial of service via memory exhaustion. 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.
import gzip, zapros
# Server returns ~1 GiB of zeros gzip-compressed to ~1 MiB,
# with header: Content-Encoding: gzip
bomb = gzip.compress(b"\0" * 1_000_000_000) # ~1 MiB on the wire
with zapros.stream("GET", "https://malicious.example/bomb") as response:
# Caller asks for 8 KiB chunks, expecting bounded memory:
for chunk in response.iter_bytes(chunk_size=8192):
... # first `chunk` is ~1 GiB, not 8 KiB -> memory exhaustion
Patches
Upgrade to 0.14.0 or later. The decoders now bound the output of each decompression step to the requested chunk_size: gzip/deflate via zlib's max_length + unconsumed_tail, brotli via output_buffer_limit, and zstd via a bounded stream_writer. Peak memory during streaming decode is now proportional to chunk_size for all supported encodings.
Workarounds
For unpatched versions:
- 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'smax_length), aborting once a configured limit is exceeded. - Where feasible,…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-61652 has been found in zapros.
Attackers can target a specific entry point like chunk over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade zapros to 0.14.0 or later.
If unsure, ask your IT team or search "zapros CVE-2026-61652" on the vendor's site.
CVE-2026-61652 (zapros) — CWE-770
Attack surface: chunk / chunk_size / zlib / max_length
Patched: 0.14.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-770) exists in zapros. Attackers reach the vulnerable code path via chunk.
Check the vendor advisory for the affected versions of zapros. Attack surface: chunk / chunk_size / zlib / max_length.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.14.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'zapros' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'zapros' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
zaprosを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade zapros to 0.14.0ステージング環境で 0.14.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- package pypi.org
- web github.com
- web github.com
- web github.com