p PatchFirst

PatchFirst · Свежие уязвимости

Уязвимости python-aiohttp · Страница 2

За последние 30 дней в python-aiohttp опубликовано уязвимостей: 7; в каталоге KEV: 0.

Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 32

  1. CVE-2026-34993

    Средний · CVSS 6.4EPSS 0,18%Нет опубликованного исправления

    AIOHTTP Vulnerable to Deserialization of Untrusted Data

    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.

    Опубликовано Обновлено
  2. CVE-2026-34525

    Средний · CVSS 6.3EPSS 0,29%Нет опубликованного исправления

    AIOHTTP: Duplicate Host header accepted

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, multiple Host headers were allowed in aiohttp. This issue has been patched in version 3.13.4.

  3. CVE-2026-34520

    Низкий · CVSS 2.7EPSS 0,46%Нет опубликованного исправления

    AIOHTTP: C parser (llhttp) accepts null bytes and control characters in response header values - header injection / security bypass

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, the C parser (the default for most installs) accepted null bytes and control characters in response headers. This issue has been patched in version 3.13.4.

    Опубликовано Обновлено
  4. CVE-2026-34519

    Низкий · CVSS 2.7EPSS 0,29%Нет опубликованного исправления

    AIOHTTP: HTTP response splitting via \r in reason phrase

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, an attacker who controls the reason parameter when creating a Response may be able to inject extra headers or similar exploits. This issue has been patched in version 3.13.4.

    Опубликовано Обновлено
  5. CVE-2026-34518

    Низкий · CVSS 2.7EPSS 0,34%Нет опубликованного исправления

    AIOHTTP: Cookie and Proxy-Authorization headers leaked on cross-origin redirect

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, when following redirects to a different origin, aiohttp drops the Authorization header, but retains the Cookie and Proxy-Authorization headers. This issue has been patched in version 3.13.4.

    Опубликовано Обновлено
  6. CVE-2026-34517

    Низкий · CVSS 2.7EPSS 0,38%Нет опубликованного исправления

    AIOHTTP: Late size enforcement for non-file multipart fields causes memory DoS

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, for some multipart form fields, aiohttp read the entire field into memory before checking client_max_size. This issue has been patched in version 3.13.4.

  7. CVE-2026-34516

    Средний · CVSS 6.6EPSS 0,44%Есть исправление

    AIOHTTP: Multipart Header Size Bypass

    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.

    • Обновитесь до 3.13.3-3ubuntu1+esm1
    Опубликовано Обновлено
  8. CVE-2026-34514

    Низкий · CVSS 2.7EPSS 0,32%Есть исправление

    AIOHTTP: CRLF injection in multipart part content type header construction

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, an attacker who controls the content_type parameter in aiohttp could use this to inject extra headers or similar exploits. This issue has been patched in version 3.13.4.

    • Обновитесь до 3.13.3-3ubuntu1+esm1
    Опубликовано Обновлено
  9. CVE-2026-22815

    Средний · CVSS 6.9EPSS 0,44%Есть исправление

    AIOHTTP: Uncapped memory usage possible through aiohttp allowing unlimited trailer headers

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, insufficient restrictions in header/trailer handling could cause uncapped memory usage. This issue has been patched in version 3.13.4.

    • Обновитесь до 3.13.3-3ubuntu1+esm1
    Опубликовано Обновлено
  10. CVE-2026-34513

    Низкий · CVSS 2.7EPSS 0,44%Есть исправление

    AIOHTTP: Denial of Service (DoS) via Unbounded DNS Cache in TCPConnector

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.13.4, an unbounded DNS cache could result in excessive memory usage possibly resulting in a DoS situation. This issue has been patched in version 3.13.4.

    • Обновитесь до 3.13.3-3ubuntu1+esm1
  11. CVE-2025-53643

    Низкий · CVSS 1.7EPSS 0,36%Нет опубликованного исправления

    AIOHTTP is vulnerable to HTTP Request/Response Smuggling through incorrect parsing of chunked trailer sections

    AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.12.14, the Python parser is vulnerable to a request smuggling vulnerability due to not parsing trailer sections of an HTTP request. If a pure Python version of aiohttp is installed (i.e. without the usual C extensions) or AIOHTTP_NO_EXTENSIONS is enabled, then an attacker may be able to execute a request smuggling attack to bypass certain firewalls or proxy protections. Version 3.12.14 contains a patch for this issue.

  12. CVE-2024-23334

    Средний · CVSS 5.9EPSS 76,88%Публичный эксплойтНет опубликованного исправления

    aiohttp.web.static(follow_symlinks=True) is vulnerable to directory traversal

    aiohttp is an asynchronous HTTP client/server framework for asyncio and Python. When using aiohttp as a web server and configuring static routes, it is necessary to specify the root path for static files. Additionally, the option 'follow_symlinks' can be used to determine whether to follow symbolic links outside the static root directory. When 'follow_symlinks' is set to True, there is no validation to check if reading a file is within the root directory. This can lead to directory traversal vulnerabilities, resulting in unauthorized access to arbitrary files on the system, even when symlinks are not present. Disabling follow_symlinks and us

    Опубликовано Обновлено

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →