When processed, the library fails to properly throttle or limit the number of file descriptors created on behalf of the request, allowing an attacker to exhaust the operating system's file descriptor limits. This leads to a denial-of-service (DoS) condition where the affected application becomes unresponsive or unable to handle new network connections or file operations. Defenders should prioritize updating to aiohttp 3.14.4 or later to implement the necessary resource constraints.

Attack Chain

1. The attacker identifies an internet-facing application that uses the aiohttp library for handling HTTP multipart/form-data uploads.
2. The attacker crafts a malicious HTTP POST request containing an excessive number of multipart parts or specific header values designed to trigger the vulnerable code path in Request.post().
3. The target application receives the malicious request and initiates the parsing process within the aiohttp multipart handler.
4. The library allocates file descriptors for each part of the multipart request without enforcing per-request limits.
5. The attacker sustains the transmission of these requests to rapidly increase the count of open file descriptors associated with the application process.
6. The application process reaches the operating system's configured maximum file descriptor limit (ulimit).
7. The application service crashes or becomes unresponsive to legitimate users, resulting in a successful denial-of-service.

Impact

Successful exploitation results in the unavailability of the web service. This vulnerability impacts any system utilizing aiohttp 2.0.0 through 3.14.3 to process multipart requests, potentially affecting a wide array of web services, internal APIs, and microservices. Because the attack requires no authentication and low complexity, it presents a significant risk for service disruption in environments exposed to untrusted network traffic.

Recommendation

• Upgrade the aiohttp package to version 3.14.4 or later immediately.
• Monitor web server error logs for persistent "too many open files" or "OSError: [Errno 24] Too many open files" messages, which may indicate active exploitation or resource exhaustion.
• Review network edge configurations to implement rate limiting on POST requests directed at multipart/form-data endpoints.
• Use system-level telemetry to monitor file descriptor usage per application process, specifically for services using the affected aiohttp versions.