aio-libs aiohttp up to 3.13.x CookieJar.load deserialization

Summaryinfo

A vulnerability was found in aio-libs aiohttp up to 3.13.x. It has been rated as problematic. This issue affects the function CookieJar.load. This manipulation causes deserialization. This vulnerability appears as CVE-2026-34993. The attack requires local access. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in aio-libs aiohttp up to 3.13.x. It has been declared as problematic. Affected by this vulnerability is the function CookieJar.load. The manipulation with an unknown input leads to a deserialization vulnerability. The CWE definition for the vulnerability is CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.14.0, using ``CookieJar.load()`` with untrusted input may allow arbitrary code execution. Most applications using this function will be doing so with the user's own data, so this is unlikely to affect many applications. Version 3.14.0 patches the issue. If an application does allow attacker controlled files to be loaded, a workaround on older releases would be to sanitize the files before loading.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-34993 since 03/31/2026. The exploitation appears to be difficult. An attack has to be approached locally. Additional levels of successful authentication are necessary for exploitation. Technical details are known, but no exploit is available.

Upgrading to version 3.14.0 eliminates this vulnerability. Applying the patch dcf40f30637e8752c76781cf6703b5a236749a00 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 EUVD (EUVD-2026-34001). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• aio-libs

Name

• aiohttp

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7
• 3.8
• 3.9
• 3.10
• 3.11
• 3.12
• 3.13

License

• open-source

Website

• Product: https://github.com/aio-libs/aiohttp/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion