CVE-2026-70646

CVE-2026-70646 is a high-severity uncontrolled resource consumption vulnerability in aiosend (pip), affecting versions < 3.0.7. It is fixed in 3.0.7.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

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.

Severity

High (CVSS 7.5)

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected Package

  • Ecosystem: PyPI
  • Package: aiosend

Affected Versions

  • < 3.0.6

Patched Versions

  • >= 3.0.6

Details

In aiosend/webhook/base.py, WebhookHandler.feed_update() performs full Pydantic deserialization before validating the webhook signature:

update = Update.model_validate(body, context={"client": self})
if not self._check_signature(body, headers):
    return False

Because authentication occurs only after parsing, anyone can send arbitrarily large JSON payloads with an invalid signature. Although the request is rejected, the server still performs all parsing work.

Additionally, CryptoPayObject is configured with:

ConfigDict(extra="allow")

allowing arbitrary extra fields to be retained in memory, increasing resource consumption.

Affected Components

  • aiosend/webhook/base.py
  • aiosend/types/base.py
  • AiohttpManager
  • FastAPIManager
  • FlaskManager

Workarounds

Until upgrading:

  • Restrict request body size at the reverse proxy or web framework.
  • Rate-limit webhook endpoints.
  • Reject oversized requests before JSON parsing.

CWE

  • CWE-400: Uncontrolled Resource Consumption

Impact

An unauthenticated attacker can repeatedly send large invalid webhook requests, forcing the server to consume CPU time and memory before rejecting them.

This results in a pre-authentication denial-of-service condition affecting all webhook integrations.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2026-70646 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.7); upgrading removes the vulnerable code path.

Affected versions

aiosend (< 3.0.7)

Security releases

aiosend → 3.0.7 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade to aiosend 3.0.6 or later.

Frequently Asked Questions

  1. What is CVE-2026-70646? CVE-2026-70646 is a high-severity uncontrolled resource consumption vulnerability in aiosend (pip), affecting versions < 3.0.7. It is fixed in 3.0.7. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
  2. How severe is CVE-2026-70646? CVE-2026-70646 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of aiosend are affected by CVE-2026-70646? aiosend (pip) versions < 3.0.7 is affected.
  4. Is there a fix for CVE-2026-70646? Yes. CVE-2026-70646 is fixed in 3.0.7. Upgrade to this version or later.
  5. Is CVE-2026-70646 exploitable, and should I be worried? Whether CVE-2026-70646 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-70646 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-70646? Upgrade aiosend to 3.0.7 or later.

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo