CVE-2026-34993: AIOHTTP Vulnerable to Deserialization of Untrusted Data

Published Jun 2, 2026
·
Updated

Summary

Using CookieJar.load() with untrusted input may allow arbitrary code execution.

Impact

Most applications using this function will be doing so with the user's own data, so this is unlikely to affect many applications.

Workaround

If an application does allow attacker controlled files to be loaded, a workaround on older releases would be to sanitise the files before loading.

-----

Patch: https://github.com/aio-libs/aiohttp/commit/dcf40f30637e8752c76781cf6703b5a236749a00

Other sources

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.

NVD

Affected Software

3 affected componentsFixes available
pypi/aiohttp<3.14.0
pip/aiohttp<3.14.0
3.14.0
aiohttp aiohttp<3.14.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.0
  2. Upgrade

    Upgrade aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.0Patch dcf40f30637e8752c76781cf6703b5a236749a00
  3. Configuration

    On releases prior to 3.14.0, if applications use CookieJar.load() with attacker-controlled (untrusted) input, sanitize the files before loading.

    aiohttp.CookieJar load() input handling = Sanitize files before loading

Event History

Jun 2, 2026
CVE Published
via MITRE·06:29 PM
Data Sourced
via MITRE·06:29 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·08:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·08:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 3, 2026
Advisory Published
via GitHub·08:56 PM
Data Sourced
via GitHub·08:56 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-34993?

The severity of CVE-2026-34993 is medium with a score of 6.4.

2

What vulnerability is identified by CVE-2026-34993?

CVE-2026-34993 is a deserialization vulnerability in AIOHTTP that can lead to arbitrary code execution when using untrusted input with CookieJar.load().

3

How do I fix CVE-2026-34993?

To fix CVE-2026-34993, update AIOHTTP to version 3.14.0 or later, which addresses this security risk.

4

What is the impact of CVE-2026-34993?

CVE-2026-34993 can potentially allow attackers to execute arbitrary code within applications using vulnerable versions of AIOHTTP.

5

Who is affected by CVE-2026-34993?

Users of AIOHTTP versions prior to 3.14.0 who use CookieJar.load() with untrusted data may be affected by CVE-2026-34993.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203