CVE-2026-70646: CWE-400: Uncontrolled Resource Consumption in vovchic17 aiosend
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.
AI Analysis
Technical Summary
The vulnerability in aiosend (CVE-2026-70646) involves uncontrolled resource consumption (CWE-400) due to the WebhookHandler.feed_update() method deserializing the entire JSON request body before HMAC signature verification. This design flaw allows unauthenticated attackers to force the server to perform expensive parsing operations on arbitrary JSON payloads that will ultimately be rejected, resulting in unnecessary CPU and memory consumption. The issue affects versions prior to 3.0.7, which includes all versions less than 3.0.7. The vulnerability has a CVSS 3.1 base score of 7.5 (high severity), with network attack vector, low attack complexity, no privileges required, no user interaction, and impacts availability only. No known exploits in the wild have been reported. The vendor fixed the issue in version 3.0.7. Workarounds include limiting request body size and rate-limiting webhook endpoints to mitigate resource exhaustion risks.
Potential Impact
An unauthenticated attacker can cause excessive CPU and memory consumption on affected systems by sending large or complex JSON payloads to the webhook endpoint. This can lead to denial of service conditions due to resource exhaustion. The vulnerability does not impact confidentiality or integrity but affects availability.
Mitigation Recommendations
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.
CVE-2026-70646: CWE-400: Uncontrolled Resource Consumption in vovchic17 aiosend
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.
CVSS v3.1
Score 7.5high
Affected software
vovchic17
aiosend
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in aiosend (CVE-2026-70646) involves uncontrolled resource consumption (CWE-400) due to the WebhookHandler.feed_update() method deserializing the entire JSON request body before HMAC signature verification. This design flaw allows unauthenticated attackers to force the server to perform expensive parsing operations on arbitrary JSON payloads that will ultimately be rejected, resulting in unnecessary CPU and memory consumption. The issue affects versions prior to 3.0.7, which includes all versions less than 3.0.7. The vulnerability has a CVSS 3.1 base score of 7.5 (high severity), with network attack vector, low attack complexity, no privileges required, no user interaction, and impacts availability only. No known exploits in the wild have been reported. The vendor fixed the issue in version 3.0.7. Workarounds include limiting request body size and rate-limiting webhook endpoints to mitigate resource exhaustion risks.
Potential Impact
An unauthenticated attacker can cause excessive CPU and memory consumption on affected systems by sending large or complex JSON payloads to the webhook endpoint. This can lead to denial of service conditions due to resource exhaustion. The vulnerability does not impact confidentiality or integrity but affects availability.
Mitigation Recommendations
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.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-04T21:48:08.612Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a749d44bf8831d539dba904
Added to database: 08/06/2026, 14:42:12 UTC
Last enriched: 08/13/2026, 16:46:03 UTC
Last updated: 09/18/2026, 02:10:50 UTC
Views: 59
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.