GHSA-7m8f-hgjq-8gc9 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in aiosend. A fix is available for aiosend — see the affected versions and patch details below.
aiosend: Deserialization of request body before signature verification (Pre-auth DoS) in webhook handler
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-7m8f-hgjq-8gc9.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-7m8f-hgjq-8gc9 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
aiosendReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
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.
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.
Affected Components
aiosend/webhook/base.pyaiosend/types/base.pyAiohttpManagerFastAPIManagerFlaskManager
Workarounds
Until upgrading:
- Restrict request body size at the reverse proxy or web framework.
- Rate-limit webhook endpoints.
- Reject oversized requests before JSON parsing.
Solution
Upgrade to aiosend 3.0.6 or later.
CWE
- CWE-400: Uncontrolled Resource Consumption
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | aiosend | all versions | 3.0.7pip install --upgrade 'aiosend==3.0.7' |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aiosend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aiosend to 3.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7m8f-hgjq-8gc9 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7m8f-hgjq-8gc9 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-7m8f-hgjq-8gc9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-7m8f-hgjq-8gc9 in your dependencies?
O3 Security finds GHSA-7m8f-hgjq-8gc9 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.