CVE-2026-70646Patch

LOWCVSS 7.5 · HIGH

Signal is active with 1 mentions in latest observed window

Immediate actions

Patch affected systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD 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.

Back to dashboard

0.5/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-400

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Threat summary

Patch or workaround signal is available
1 mentions across 1 observed day

What's happening

Patch or workaround mentioned in 1 signal
Technical details provided in 1 signal
1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d

Signal classification1 categories

Patch

1100.0%

Full discourse1 post

CyberSignal | Cybersecurity News@XQOPTRX46d
Patch
💰 Crypto Pay Python client vulnerable to DoS CVE-2026-70646 affects aiosend <3.0.7. Webhook requests are fully deserialized before HMAC verification, letting unauthenticated attackers force expensive JSON parsing and consume CPU/memory. ✅ Fixed: 3.0.7 🔎 Source: Tenable / GitHub Advisory #Python #DoS #AppSec #CyberSecurity
Post summary
CVE‑2026‑70646 is a DoS vulnerability in Crypto Pay Python client due to unauthenticated JSON deserialization; it is fixed in version 3.0.7.
0000044
34 followersView on X

Explore more

Back to dashboard