aio-libs aiohttp up to 3.13.3 allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 1.45- |
Summary
A vulnerability was found in aio-libs aiohttp up to 3.13.3. It has been rated as problematic. Affected by this issue is some unknown functionality. Performing a manipulation results in allocation of resources. This vulnerability is known as CVE-2026-34516. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability was found in aio-libs aiohttp up to 3.13.3. It has been classified as problematic. This affects an unknown function. The manipulation with an unknown input leads to a allocation of resources vulnerability. CWE is classifying the issue as CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. This is going to have an impact on availability. The summary by CVE is:
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, a response with an excessive number of multipart headers may be allowed to use more memory than intended, potentially allowing a DoS vulnerability. This issue has been patched in version 3.13.4.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-34516 since 03/30/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
Upgrading to version 3.13.4 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 8a74257b3804c9aac0bf644af93070f68f6c5a6f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at CNNVD (CNNVD-202604-221). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Product: https://github.com/aio-libs/aiohttp/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: aiohttp 3.13.4
Patch: 8a74257b3804c9aac0bf644af93070f68f6c5a6f
Timeline
03/30/2026 CVE reserved04/02/2026 Advisory disclosed
04/02/2026 VulDB entry created
04/02/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-m5qp-6w8w-w647
Status: Confirmed
CVE: CVE-2026-34516 (🔒)
GCVE (CVE): GCVE-0-2026-34516
GCVE (VulDB): GCVE-100-354795
CNNVD: CNNVD-202604-221 - aiohttp 安全漏洞
Entry
Created: 04/02/2026 02:39Updated: 04/02/2026 18:48
Changes: 04/02/2026 02:39 (70), 04/02/2026 18:48 (6)
Complete: 🔍
Cache ID: 216:E42:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.