CVE-2026-70646

aiosend: Deserialization of request body before signature verification (Pre-auth DoS) in webhook handler

Published Aug 6, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability arises from aiosend's webhook handler deserializing JSON request bodies before verifying their HMAC signature, allowing an unauthenticated attacker to send large, complex JSON payloads that consume excessive CPU and memory before being rejected. This uncontrolled resource consumption can degrade system performance and cause denial of service. The weakness is classified as CWE‑400, representing an uncontrolled resource consumption flaw.

Affected Systems

All versions of vovchic17's aiosend older than 3.0.7 are affected, including the 3.0.6 and earlier releases. The issue was fixed in v3.0.7, so upgrading to that or later versions removes the vulnerability. Systems exposing the webhook endpoint to untrusted clients are at risk.

Risk and Exploitability

The CVSS score of 7.5 reflects a high risk level, and the lack of an EPSS score does not diminish the potential for exploitation by attackers who can target the exposed webhook. As the flaw permits unauthenticated requests to trigger resource exhaustion, the attack vector is network-based, leveraging standard HTTP traffic to submit oversized JSON payloads. The vulnerability is not listed in the CISA KEV catalog, but the severity and potential impact warrant immediate attention.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade aiosend to v3.0.7 or newer to apply the signature verification before JSON parsing.
  • If upgrade is not immediately possible, constrain request sizes at the reverse proxy or application layer, enforce rate limiting, and drop oversized requests before attempting deserialization.
  • Monitor webhook traffic for unusually large or malformed requests and temporarily block or rate‑limit sources that exhibit repeated abuse.

Generated by OpenCVE AI on August 6, 2026 at 15:58 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-7m8f-hgjq-8gc9 aiosend: Deserialization of request body before signature verification (Pre-auth DoS) in webhook handler
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Vovchic17
Vovchic17 aiosend
Vendors & Products Vovchic17
Vovchic17 aiosend
Type Values Removed Values Added
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.
Title aiosend: Deserialization of request body before signature verification (Pre-auth DoS) in webhook handler
Weaknesses CWE-400
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 8, 2026, 2:03 AM
Reserved
Aug 4, 2026, 9:48 PM
Status
Deferred
Published
Aug 6, 2026, 3:17 PM
Modified
Oct 23, 2026, 9:10 PM