AIOHTTP's C parser (llhttp) accepts null bytes and control characters in response header values - header injection/security bypass
GHSA-63hf-3vf5-4wqf · CVE-2026-34520 · PYSEC-2026-2102
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Summary
The C parser (the default for most installs) accepted null bytes and control characters in request headers.
Impact
An attacker could send header values that are interpreted differently than expected due to the presence of control characters. For example, request.url.origin() may return a different value than the raw Host header, or what a reverse proxy interpreted it as., potentially resulting in some kind of security bypass.
Patch: https://github.com/aio-libs/aiohttp/commit/9370b9714a7a56003cacd31a9b4ae16eab109ba4
References
- WEB https://github.com/aio-libs/aiohttp/security/advisories/GHSA-63hf-3vf5-4wqf
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-34520
- WEB https://github.com/aio-libs/aiohttp/commit/9370b9714a7a56003cacd31a9b4ae16eab109ba4
- PACKAGE https://github.com/aio-libs/aiohttp
- WEB https://github.com/aio-libs/aiohttp/releases/tag/v3.13.4
- WEB https://github.com/pypa/advisory-database/tree/main/vulns/aiohttp/PYSEC-2026-2102.yaml
Ready to move
Start Securing
Free, no credit card | First findings in minutes