CVE-2026-34520

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

Published Apr 1, 2026 CVSS 4.0 · 2.7 Low EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability in AIOHTTP's default C parser allows the inclusion of null bytes and control characters in response header values, enabling header injection and potential security bypass. This improper handling of header data aligns with CWE‑113 (HTTP Response Splitting) and CWE‑1286 (Control characters in header values), and can lead to protocol manipulation or unintended response behavior.

Affected Systems

AIOHTTP releases prior to version 3.13.4 are affected when using the default C parser. This applies to all installations that rely on the C based parser for HTTP response parsing.

Risk and Exploitability

With a CVSS score of 2.7, the vulnerability carries a low impact assessment and no publicly available EPSS data suggests widespread exploitation. Attackers could remotely craft responses containing null or control characters, but success relies on the vulnerable parser and does not typically lead to high‑severity outcomes unless combined with other weaknesses.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade aiohttp to version 3.13.4 or later
  • If an upgrade is not immediately possible, validate and sanitize all HTTP response header values before processing to eliminate null bytes and control characters

Generated by OpenCVE AI on April 2, 2026 at 02:40 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4613-1 python-aiohttp security update
Debian DLA Debian DLA DLA-4876-1 python-aiohttp security update
Github GHSA Github GHSA GHSA-63hf-3vf5-4wqf AIOHTTP's C parser (llhttp) accepts null bytes and control characters in response header values - header injection/security bypass
History
Type Values Removed Values Added
First Time appeared Aiohttp
Aiohttp aiohttp
CPEs cpe:2.3:a:aiohttp:aiohttp:*:*:*:*:*:*:*:*
Vendors & Products Aiohttp
Aiohttp aiohttp
Type Values Removed Values Added
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H'}

Type Values Removed Values Added
First Time appeared Aio-libs
Aio-libs aiohttp
Vendors & Products Aio-libs
Aio-libs aiohttp
Type Values Removed Values Added
Weaknesses CWE-1286
References
Metrics threat_severity

None

cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N'}

threat_severity

Low

Type Values Removed Values Added
Description 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.
Title AIOHTTP: C parser (llhttp) accepts null bytes and control characters in response header values - header injection / security bypass
Weaknesses CWE-113
References
Metrics cvssV4_0

{'score': 2.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U'}

Weaknesses
  • CWE-113

    Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')

  • CWE-1286

    Improper Validation of Syntactic Correctness of Input

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Apr 4, 2026, 3:13 AM
Reserved
Mar 30, 2026, 4:03 PM
Status
Analyzed
Published
Apr 1, 2026, 9:17 PM
Modified
Oct 26, 2026, 9:10 PM
Severity
Low
Public date
Apr 1, 2026, 8:27 PM