CVE-2026-70646: vovchic17 aiosend · Uncontrolled Resource Consumption
Affects vovchic17 aiosendSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 3.0.6 soon.
Data as of 5 Nov 2026, 00:01 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 50% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.0.6, 3.0.7
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.
What to do
Upgrade aiosend to 3.0.6; vovchic17/aiosend to 3.0.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vovchic17aiosend | Affected
| Fixed in
|
GitHubvovchic17/aiosendpkg:github/vovchic17/aiosendOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Version 3.0.7 of aiosend fixes this vulnerability. Users should upgrade to version 3.0.7 or later. Until upgrading, mitigations include restricting the request body size at the reverse proxy or web framework level, rate-limiting webhook endpoints, and rejecting oversized requests before JSON parsing to reduce the risk of resource exhaustion.
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.