CVE-2026-70646

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (49th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 22, 2026

Last Modified

September 18, 2026

Advisory Details (3)

Auto-updated Aug 6, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Deserialization of request body before signature verification (Pre-auth DoS) in webhook handler · Advisory · vovchic17/aiosend · GitHub

https://github.com/vovchic17/aiosend/security/advisories/GHSA-7m8f-hgjq-8gc9
GitHub release Patch Available

v3.0.7

Patch available: vovchic17/aiosend v3.0.7

https://github.com/vovchic17/aiosend/releases/tag/v3.0.7
GitHub commit Patch Available

commit db20f0a74220 (vovchic17/aiosend)

Patch available: vovchic17/aiosend v3.0.7 (contains commit db20f0a74220)

https://github.com/vovchic17/aiosend/commit/db20f0a742209dfac181863d398ec5112687efa4

Vendor Advisories for CVE-2026-70646(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
aiosend0.1.14 ... 3.0.6 (23 versions)
  • every version up to 3.0.7: fixed in 3.0.7
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 76 are merged into the row they repeat.

  1. 2026-10-11 19:29 UTCEG score recompute
  2. 2026-10-11 16:44 UTCEG score recompute
  3. 2026-10-11 14:04 UTCEG score recompute
  4. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  7. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-08 15:05 UTCOSV refresh
  9. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  10. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  11. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  12. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  13. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  14. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  15. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  16. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  17. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  18. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  19. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  20. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-09-18 20:37 UTCEG score recompute
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 28th percentile
Show 49 more
  1. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  2. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  3. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  4. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  5. 2026-09-11 03:53 UTCOSV refresh
  6. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  7. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  8. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  9. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  10. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  11. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  12. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  13. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  14. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-08-23 16:41 UTCEG score recompute
  21. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  23. 2026-08-21 21:41 UTCEG score recompute
  24. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  25. 2026-08-20 18:39 UTCEG score recompute
  26. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  27. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  28. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  29. 2026-08-16 16:48 UTCEG score recompute
  30. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  31. 2026-08-16 03:19 UTCEG score recompute
  32. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  33. 2026-08-15 01:31 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  34. 2026-08-14 01:53 UTCEG score recompute
  35. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  36. 2026-08-12 14:12 UTCEG score recompute
  37. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  38. 2026-08-11 13:46 UTCEG score recompute
  39. 2026-08-11 00:29 UTCEG score recompute
  40. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  41. 2026-08-10 00:05 UTCEG score recompute
  42. 2026-08-09 13:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  43. 2026-08-09 01:24 UTCEG score recompute
  44. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  45. 2026-08-08 02:20 UTCEG score recompute
  46. 2026-08-08 02:12 UTCEG score recompute
  47. 2026-08-08 01:45 UTCEG score recompute
  48. 2026-08-06 15:30 UTCEG score recompute
  49. 2026-08-06 14:41 UTCEG score recomputeFirst assessed: 7.5 HIGH

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-70646?
CVE-2026-70646 is a high-severity vulnerability; its CVE record was published on May 22, 2026. 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…
When was the CVE record for CVE-2026-70646 published?
The CVE record for CVE-2026-70646 was published on May 22, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 18, 2026; the record at its source may have been updated since.
Is CVE-2026-70646 actively exploited?
CVE-2026-70646 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-70646?
CVE-2026-70646 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-70646?
A fix for CVE-2026-70646 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-70646 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-70646

Explore →

Is Your Infrastructure Affected by CVE-2026-70646?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs