{"answers":{"affected":"3 open source packages ship an affected version, including zapros.","exploited":"There is no known exploitation of CVE-2026-61652 in the wild and no public exploit code.","fix":"Upgrade zapros to 0.14.0 or later.","what":"CVE-2026-61652 is a high-severity denial of service vulnerability in kap-sh zapros, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-61652 and fix it if it is affected.\n\nWhat it is: CVE-2026-61652 is a high-severity denial of service vulnerability in kap-sh zapros, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-61652 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- zapros (PyPI): affected all versions; fixed in 0.14.0\n- zapros (PyPI): affected all versions; fixed in 0.14.0\n- zapros (PyPI): affected all versions; fixed in 0.14.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-61652/ (Markdown: https://insights.sbomify.com/CVE-2026-61652/index.md)","id":"CVE-2026-61652","markdown":"https://insights.sbomify.com/CVE-2026-61652/index.md","name":"CVE-2026-61652","record":{"aliases":["GHSA-6cp7-3m3c-5x5c","PYSEC-2026-4182"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python HTTP client","requires_auth":"none","summary":"A malicious server can cause memory exhaustion in Zapros by sending a compressed response that ignores chunk size limits, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Zapros: Streaming decoders ignored the requested chunk size, allowing a single compressed response chunk to allocate unbounded memory (decompression bomb)","id":"CVE-2026-61652","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Lightdash: Unauthenticated dbt Cloud webhook with path injection leaks API key","id":"CVE-2026-61654"},"packages":[{"ecosystem":"PyPI","fixed":["0.14.0"],"introduced":["0"],"last_affected":[],"package":"zapros","purl":null,"source":"GHSA-6cp7-3m3c-5x5c"},{"ecosystem":"PyPI","fixed":["0.14.0"],"introduced":["0"],"last_affected":[],"package":"zapros","purl":"pkg:pypi/zapros","source":"GHSA-6cp7-3m3c-5x5c"},{"ecosystem":"PyPI","fixed":["0.14.0"],"introduced":["0"],"last_affected":[],"package":"zapros","purl":"pkg:pypi/zapros","source":"PYSEC-2026-4182"}],"prev":{"headline":"@roomi-fields/notebooklm-mcp has a path traversal in vault.batch tool that allows arbitrary file write outside intended vault directory","id":"CVE-2026-61647"},"products":["zapros"],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-22","vendors":["kap-sh"]},"summary":"A malicious server can cause memory exhaustion in Zapros by sending a compressed response that ignores chunk size limits, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2026-61652/"}