{"answers":{"affected":"3 open source packages ship an affected version, including aiosend.","exploited":"There is no known exploitation of CVE-2026-70646 in the wild and no public exploit code.","fix":"Upgrade aiosend to 3.0.7 or later.","what":"CVE-2026-70646 is a high-severity denial of service vulnerability in vovchic17 aiosend, published on 6 Aug 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-70646 and fix it if it is affected.\n\nWhat it is: CVE-2026-70646 is a high-severity denial of service vulnerability in vovchic17 aiosend, published on 6 Aug 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-70646 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- aiosend (PyPI): affected all versions; fixed in 3.0.7\n- aiosend (PyPI): affected all versions; fixed in 3.0.7\n- aiosend (PyPI): affected all versions; fixed in 3.0.7\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-70646/ (Markdown: https://insights.sbomify.com/CVE-2026-70646/index.md)","id":"CVE-2026-70646","markdown":"https://insights.sbomify.com/CVE-2026-70646/index.md","name":"CVE-2026-70646","record":{"aliases":["GHSA-7m8f-hgjq-8gc9","PYSEC-2026-3626"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Crypto Pay API client","requires_auth":"none","summary":"Unauthenticated attackers can cause denial of service in aiosend by sending large JSON payloads that are parsed before signature verification.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"aiosend is a synchronous and asynchronous Crypto Pay API client. Pror to version 3.0.7, `WebhookHandler.feed_update()` deserializes the entire request body before verifying the HMAC signature. This allows an unauthenticated attacker to force expensive parsing of arbitrary JSON payloads that will ultimately be rejected, leading to unnecessary CPU and memory consumption. Version 3.0.7 fixes the issue. Some workarounds are available. Restrict request body size at the reverse proxy or web framework, rate-limit webhook endpoints, and/or reject oversized requests before JSON parsing.","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":"aiosend: Deserialization of request body before signature verification (Pre-auth DoS) in webhook handler","id":"CVE-2026-70646","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Cross-site scripting in GetSimpleCMS-CE","id":"CVE-2026-70650"},"packages":[{"ecosystem":"PyPI","fixed":["3.0.7"],"introduced":["0"],"last_affected":[],"package":"aiosend","purl":null,"source":"GHSA-7m8f-hgjq-8gc9"},{"ecosystem":"PyPI","fixed":["3.0.7"],"introduced":["0"],"last_affected":[],"package":"aiosend","purl":"pkg:pypi/aiosend","source":"GHSA-7m8f-hgjq-8gc9"},{"ecosystem":"PyPI","fixed":["3.0.7"],"introduced":["0"],"last_affected":[],"package":"aiosend","purl":"pkg:pypi/aiosend","source":"PYSEC-2026-3626"}],"prev":{"headline":"llama.cpp b1886–b7445 Race Condition Use-After-Free via llama-android.cpp","id":"CVE-2026-70640"},"products":["aiosend"],"published":"2026-08-06","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-08-08","vendors":["vovchic17"]},"summary":"Unauthenticated attackers can cause denial of service in aiosend by sending large JSON payloads that are parsed before signature verification.","url":"https://insights.sbomify.com/CVE-2026-70646/"}