CVE-2026-70646
Received Received - Intake

aiosend WebhookHandler JSON Parsing DoS Vulnerability

Publication date: 2026-08-06

Last updated on: 2026-08-06

Assigner: GitHub, Inc.

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-06
Last Modified
2026-08-06
Generated
2026-08-06
AI Q&A
2026-08-06
EPSS Evaluated
N/A
NVD
CVE-2026-70646
EUVD
EUVD-2026-53920

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
aiosend crypto_pay_api_client to 3.0.7 (inc)
vovchic17 aiosend to 3.0.7 (exc)
vovchic17 aiosend 3.0.7

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-400 The product does not properly control the allocation and maintenance of a limited resource.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

aiosend is a Crypto Pay API client. The vulnerability exists in versions before 3.0.7 where WebhookHandler.feed_update() deserializes the entire request body before verifying the HMAC signature. This allows unauthenticated attackers to send large JSON payloads that consume excessive CPU and memory before being rejected.

Detection Guidance

Detecting this vulnerability requires monitoring for unusual CPU or memory usage spikes from JSON parsing operations. Check webhook endpoints for requests with large payloads that are rejected after parsing. Inspect logs for repeated failed HMAC verification attempts.

Impact Analysis

An attacker could exploit this to cause denial-of-service by consuming server resources with maliciously large JSON payloads, potentially leading to service slowdowns or crashes. Systems processing high volumes of webhooks are most at risk.

Mitigation Strategies

Upgrade aiosend to version 3.0.7 or later. As workarounds, restrict request body size at the reverse proxy, rate-limit webhook endpoints, or reject oversized requests before JSON parsing to prevent CPU exhaustion.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-70646. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart